Sql 2016 replication immediate updating subscription
Randal's blog post "In defense of transactional replication as an HA technology.") Although the learning curve for replication can be intimidating, the successful use of replication comes down to understanding the components involved.The best way to gain this understanding is to practice basic deployments, then investigate the associated user schema modifications, metadata objects, SQL Server Agent jobs, and associated agent settings.
The subscriber database can contain both replicated and nonreplicated objects and can host more than one subscription from different publications.Because of the need to have a highly available system and they could not afford to be down, they needed a way to downgrade to the old database system in case somthing bad happens to the upgraded system.Also, our customer wanted to include the disaster recovery solution.To see how we were able to accomplish this check out our video.SQL Server replication encompasses a set of capabilities that have yet to be fully replaced by other features found natively in SQL Server.And more controversially, some have even found a place for replication from a disaster recovery or high availability perspective.
(For more information about this particular subject, see Paul S.
A subscription can be defined as (data is pulled to the subscription database from the Subscriber).
Push subscriptions are more common with snapshot and transactional replication deployments.
We proposed a solution that would allow them to use data replication from the upgraded database to the old database.
So, in case of an issue in production they could easily go back to the old version of SQL Server.
Replication requires a separate database to house both metadata and in-flight data.