May 12, 2007 at 1:05 pm
In my company, we have a central database and 4 remote databases. the central database replicate same database into 4 remote database in parallel. the replication is transaction replication and the data is input in the central database and replicated into remote databases. there are some triggers in the remote database that retrieve data that was replicated from central database into other table. the design is like this. it is wierd that one of remote database is very slow and replication locking the table and client application is blocked out. the client application is hang. the replication is very slow, 4 rows/minute. other 3 remote db are ok. I don't know why only one remote db is ofen happened such thing, others were no problem. I know the triggers are bad, especially work with replication. But why other remote db were ok. I don't know if there are some other problem. can dbcc dbreindex be help? Thanks.
May 12, 2007 at 2:52 pm
I'd check in with the network guy, or the DBA that handles that server. There must be something sucking the life right off that server. My watch could update more rows than that. Make sure that there's no other program huging the machine.
May 12, 2007 at 4:22 pm
While this may sound incredibly simple, it is also incredibly common... have the network guy check the "duplex" on all the "boxes" in the connection chain to that remote server... if even one of them is set wrong, horribly slow connection. "Automatic" is NOT the connection duplex or speed that any of these should be set to because it frequently makes the wrong choice.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply