My boss set up transactional replication from one SQL Server 2008 instance to another. When he set it up it created a snapshot job that runs once an hour, and every time it runs it causes deadlocks. He's doesn't know much about replication and neither do I... can't we just disable the job? I've tried disabling it and the data still gets replicated. What is the point of even having that job at all for transactional replication?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
snapshot job for transactional replication?
- Thread starter influent1
- Start date
UpstateNYAdmin
Technical User
The snapshot job should not be run on a schedule if you are using tranactional replication. You need to the snapshot job there for reintializing the subscriptions after you add a new article. In your current setup it sounds like you are replicating all transactions and refreshing the entire table so you need to decide which approach you want to do. Disabling the snapshot job will work, and teh deadlocks should stop since the table is probably being dropped every hour when applying the newest snapshot.
- Status
Similar threads