June 30, 2008 at 6:57 am
Hello,
We have a database that we run on our server, and have now added merge replication. We have not had any performance issues on our database until the replication was implemented. The subscribers running the database have no problems, but any workstation accessing the server database has major performance issues.
Something as simple as an Update statement to set a column for one record (based an indexed field) ends up timing out after a couple of minutes. This is a statement that executes instantaneosly before replication was setup.
We've run some traces to compare what happens pre-replication and post replication, and have done things like disable the sql replication alerts, with no success.
Can anyone suggest tips/tricks that would affect database performance on the server related to replication? We've gone through the process of optimizing our db for our application before the replication, so I dont think its indexes, more what the replication is doing, since its more related to insert/updates and not select statements.
Thanks for any help,
Greg
June 30, 2008 at 7:57 am
Merge replication add triggers to all replicated tables if in addition you have custom triggers you could definitely experience a performance penalty. You should check also if rplication is using column level tracking or row level tracking.
As starting point I would check for the actual execution plan generated for those insert/update/delete statements.
* Noel
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply