February 8, 2007 at 4:10 pm
I'm having problems with slow (high latency) transactional replication from SQL Server 2005 to another server running an instance of SQL Server 2000. The strange thing is that the same publications run excellent when the subscriber is a SQL Server 7 instance running on the same machine (as the one with the problem). The volume is relatively low and we have been replicating from 2000 to 2000 for many years without any problems. The question is: Have you experienced any performance problems with transactional replication between SQL Server 2005 and SQL Server 2000?
Thanks,
Carlos.
Carlos
February 12, 2007 at 8:00 am
This was removed by the editor as SPAM
February 15, 2007 at 9:49 am
we're having a problem with one publication out of 50 or 60. SQL 2000 publisher with sql 2005 distributor and sql 2005/2000 subscribers.
best way to troubleshoot is to make sure your delivery is set up for the statements and not the default stored procedures. Sp's are too hard to read. Then turn on verbose logging on the distributor for the job and see what is being replicated.
We thought we had a problem but we are seeing a few jobs generate tens of thousands of updates and it's taking a while to replicate.
February 15, 2007 at 1:06 pm
Thanks for your reply. In my case, dropping and recreating the clustered indexes fixed the problem.
Carlos
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply