Transactional Replication for more than 500 Databases :(

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Muhammad Shariq Muzaffar - 29 Mar 2006 08:51 GMT

I have more than 500 databases on my sql server 2000 enterprise edition. I
have already suffered the deadlock problem mentioned in
http://support.microsoft.com/kb/246330

So, I tried to upgrade to sql server 2005 but still unable to implement
transactional replication for large number of databases. I have dedicated
uni processor servers for publisher, distributor and subscriber.

I think the problem still persists in sql server 2005.

Please help.

Reply to this Message

Raymond Mak [MSFT] - 29 Mar 2006 19:58 GMT

Hi Muhammad,

Since the tempdb..MSreplication_agent_status table mentioned in KB246330 is
no longer used in SQL2005, we are very much interested in any deadlock
traces if can post them here (please obfuscate any sensitive data such as
table\index names). You can use either SQL Profiler or trace flags 1204 or
1222 to gather the deadlock cycle information. If the deadlocks occur at the
subscriber database, you may be able to alleviate those by using snapshot
isolation level.

Hope that helps

-Raymond

>I have more than 500 databases on my sql server 2000 enterprise edition. I
> have already suffered the deadlock problem mentioned in
[quoted text clipped - 7 lines]
>
> Please help.

Reply to this Message