I have a question for the replication experts here:
This morning replication has stopped because of a reboot of the Subscription server.
* I did remove the publication and subscriptions.
* I made a new publication
* I made a new subscription, and let it initialize directly.
* All seems fine, replication started, and all data was transferred correctly.
After a while, we did have some production problems, some SQL-Server time-outs from client applications exactly in the period that the replication was initializing / copying data from our production (the publication server). It seems that there where some locking problems.
Can someone please inform me, how I can make sure that when I start replication, we will not have locking issues? Is this possible? Or will I always have locks on the publication server while bulk copying data / initializing the replication?
I thank you for your reply!