Contents
Is the snapshot agent used in transactional replication?
The procedures by which the Snapshot Agent implements the initial snapshot in transactional replication are the same procedures used in snapshot replication (except as outlined above with regard to concurrent snapshot processing).
Snapshot replication places shared locks on all tables published as part of replication for the duration of snapshot generation. This can prevent updates from being made on the publishing tables.
What does concurrent snapshot processing in SQL Server do?
Concurrent Snapshot Processing Snapshot replication places shared locks on all tables published as part of replication for the duration of snapshot generation. This can prevent updates from being made on the publishing tables.
How does a snapshot agent copy a cab file?
Snapshot agent creates local files, then generates a CAB file which is copied across the network to the shared folder on the Subscriber. Since compressed CAB is smaller, copy should be faster then having the Distribution Agent do a BULK INSERT across the network. You can then specify the Subscriber’s local CAB file as the Snapshot location.
Who is the subscriber in transactional replication?
The Publisher or Subscriber is a non- SQL Server database, such as Oracle. By default, Subscribers to transactional publications should be treated as read-only, because changes are not propagated back to the Publisher. However, transactional replication does offer options that allow updates at the Subscriber.
Can a Azure SQL managed instance do transactional replication?
However, transactional replication does offer options that allow updates at the Subscriber. Azure SQL Managed Instance can be a publisher, distributor, and subscriber for snapshot and transactional replication. Databases in Azure SQL Database can only be push subscribers for snapshot and transactional replication.