March 31, 2009 at 11:28 am
Ok. I've just set up my first replication that isn't a test scenario. I'm replicating all tables, views, udf's, and schema from a database that's around 25GB. The only thing I'm not replicating are the stored procedures because they were causing errors (an issue for another post). We have one linked server on the subscriber, because when I originally was trying to replicate the stored procs, some of them needed this linked server. Some of the views that are replicated also reference this linked server.
It's been running overnight, and seems to be doing fine. However, about ten minutes ago, we get a call from the company that owns the linked server. They said it was running VERY SLOW.
Now, I don't believe this should have anything to do with our replication, especially since we're not yet doing anything with the subscriber aside from letting the data replicate to it. However, we stopped the synchronization for a minute, and that company's linked server happened to speed back up.
Coincidence?
Any input would be greatly appreciated.
March 31, 2009 at 2:13 pm
Replication has as much impact on the subscriber as the activity on the primary... You can use READ_COMMITTED_SNAPSHOT to minimize locking issues with possible queries coming from the linked server but that's another topic.
* Noel
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply