CBS has expertise in SQL Server Data Redundancy Solutions. CBS has implemented some of the complicated redundancy scenerios for its clients.When SQL Server goes down, so do your profits. To ensure uninterrupted data access and productivity with continuous SQL Server data replication and rapid disaster recovery solutions from the experts at CBS.
In any replication scenario, there are two main components: Publishers have data to offer to other servers. Any given replication scheme may have one or more publishers.
Subscribers are database servers that wish to receive updates from the Publisher when data is modified. Click to see publishing model
Theres nothing preventing a single system from acting in both of these capacities. In fact, this is often done in large-scale distributed database systems. Microsoft SQL Server supports three types of database replication. This article provides a brief introduction to each of these models, while future articles will explore them in further detail. They are:
Snapshot replication acts in the manner its name implies. The publisher simply takes a snapshot of the entire replicated database and shares it with the subscribers. Of course, this is a very time and resource-intensive process. For this reason, most administrators dont use snapshot replication on a recurring basis for databases that change frequently. There are two scenarios where snapshot replication is commonly used. First, it is used for databases that rarely change. Second, it is used to set a baseline to establish replication between systems while future updates are propagated using transactional or merge replication.
Transactional replication offers a more flexible solution for databases that change on a regular basis. With transactional replication, the replication agent monitors the publisher for changes to the database and transmits those changes to the subscribers. This transmission can take place immediately or on a periodic basis.
Merge replication allows the publisher and subscriber to independently make changes to the database. Both entities can work without an active network connection. When they are reconnected, the merge replication agent checks for changes on both sets of data and modifies each database accordingly. If changes conflict with each other, it uses a predefined conflict resolution algorithm to determine the appropriate data. Merge replication is commonly used by laptop users and others who can not be constantly connected to the publisher.
Each one of these replication techniques serves a useful purpose and is well-suited to particular database scenarios. Stay tuned for future articles covering the pros and cons each technique. Click to See Data Flow in Replication
Call us at: (510)-573-5500
CBS has done an excellent job in solving redundancy issue for our NMS application which runs accross satellite. CBS suggested and implemented right solution for our Scenerio.
AAE Systems, Inc.
|< Prev||Next >|