Please Can somebody HELP - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

Import/Export (DTS) and Replication (2000)

Please Can somebody HELP

Author

Topic

kyklovod
Starting Member

4 Posts

Posted - 2002-08-09 : 05:08:19

Hi
Im not sure that someone can understand where is the problem but i will try
to explain it

There is 7 MS SQL 2000
SP2(server1,server2,server3,server4,server5,server6,server7 as examples)
servers locationed to 5 different places of our country
we have leased line between them and connection is not too bad ...But that
is not all :((
I have table named as example "get_data_1" in each SQL server.But in one of
these servers server5 that table -"get_data_1" collects data from all of
the rest servers in transactional replication.
server1 - distributor-article "get_data_1"
server2 - distributor-article "get_data_1"
server3 - distributor-article "get_data_1"
server4 - distributor-article "get_data_1"
server6 - distributor-article "get_data_1"
server7 - distributor-article "get_data_1"

and the server5 is subscriber to each of them
and the table "get_data_1" collects all the data from all location
the table is design such as there is one column which indicates location

to this point everything is sounds good but hell is right to me now

After 2 or 3 day i notice that i lost rows.I mean the table at publisher as
example server1
contains 3449 rows but select count(*) from "get_data_1" where
from_location_is_server1
returns to me 17 rows less!!!!!! I did not recieve any errors and log reader
at server1 is working fine. Replication works at all but the hell is this
mistaken rows
(3449 is not equal to 3432 )
i must reinitialized replication - and all from the beginning ... snapshot
,bulk copy and so on.. Three days pass and SQL replication says that
everything is ok but i am not blind to see that 3449 is not equal to 3432
(as example)
i also notice that not only one server from any of distributors is act like
that
is there is 5 day when server1 is fine then server3 or server6 or nevermind
....
is act in such behaviour

please help where is the mistake .... i think it is all in SQL Server 2000
platform ....
in msdn you read ONE but wneh you deploy you see SECOND and ONE is not equal
to SECOND...typical microsoft work :((((

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources