Contents
Are tables locked during generating the snapshot?
Are tables locked during snapshot generation? For transactional publications, by default the Snapshot Agent takes locks only during the initial phase of snapshot generation. For snapshot publications the Snapshot Agent takes locks during the entire snapshot generation process.
What type of locking occurs during the snapshot generation?
1) What type of locking occurs during the Snapshot generation? Locking depends on the type of replication used: In snapshot replication, the snapshot agent locks the object during the entire snapshot generation process. In transactional replication, locks are acquired initially for a very brief time and then released.
How are schema changes propagated in snapshot replication?
In snapshot replication, a new copy of the schema is sent to the Subscriber each time synchronization occurs. Therefore, all schema changes (not just those listed above) to previously published objects are automatically propagated with each synchronization.
Are there any drawbacks to SQL snapshot replication?
Drawbacks of Snapshot replication : You cannot drop/create tables, sp’s, functions, that are marked for replication. Also, you cannot directly alter a table, you have to use system stored procedures sp_repldropcolumn and sp_repladdcolumn. A standard snapshot will lock the tables during the BCP step to make sure you get a valid copy.
When does a schema change fail in transactional replication?
You cannot drop published objects, therefore the schema change fails. For transactional replication and merge replication, schema changes are propagated incrementally when the Distribution Agent or Merge Agent runs.
What is the purpose of the replication snapshot agent?
The Replication Snapshot Agent is an executable file that prepares snapshot files containing schema and data of published tables and database objects, stores the files in the snapshot folder, and records synchronization jobs in the distribution database.