Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
influent
Constraint Violating Yak Guru
367 Posts |
 Posted - 2010-11-01 : 13:36:19
|
| 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? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2010-11-02 : 12:29:13
|
| Thanks as usual Tara, you rock. Would I only need a snapshot to occur (to "catch up") if the database was experiencing heavy activity and replication couldn't keep up? Are DDL updates captured by replication without the snapshot agent? |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-11-02 : 20:28:19
|
| you only need the snapshot to run when you modify the publication, or if a fatal error occurs that the distribution agent can't recover fromsnapshot should not be configured to run on a scheduled basis in transactional replication.yed ddl changes will be applied to subscribers |
|
|
|
|
|
|
disable snapshot job?