Using SQL Server to Replicate Databases
To ensure availability and scalability for larger Commerce Server 2002 sites, you might want to replicate your Catalog database. To do this, use SQL Server to replicate your Catalog servers or server clusters inside of a Network Load Balancing (NLB) cluster. For a diagram of this configuration, see Large Site Configuration.
Use SQL Server to replicate your Commerce Server databases. Whether you are using snapshot, transactional, or merge replication, the following stages will help you implement replication.
| Stage | Tasks |
|---|---|
| Configuring replication | Identify the publisher, distributor, and subscribers in your topology. Use SQL Server Enterprise Manager, SQL-DMO, or Transact-SQL system stored procedures and scripts to configure the publisher, create a distribution database, and enable subscribers. |
| Publishing data and database objects | Create the publication and define the data and database object articles in the publication, and apply any necessary filters to data that will be published. |
| Subscribing to publications | Create push, pull, or anonymous subscriptions to indicate what publications need to be propagated to individual subscribers and when. |
| Generating the initial snapshot | Indicate where to save snapshot files, whether they are compressed, and what scripts to run before or after applying the initial snapshot. |
| Applying the initial snapshot | Apply the snapshot automatically by synchronizing the subscription using the Distribution agent or the Merge agent. The snapshot can be applied from the default snapshot folder or from removable media that can be transported manually to the subscriber before application of the snapshot. |
| Synchronizing data | Synchronizing data occurs when the Snapshot agent, Distribution agent, or Merge agent runs and updates are propagated between the publisher and subscribers.
For snapshot replication, a snapshot will be taken and propagated to subscribers. For transactional replication, the Log Reader agent will store updates in the distribution database and the Distribution agent will propagate updates to subscribers. If you are using subscriptions that can be updated with either snapshot replication or transactional replication, data will be propagated from the subscriber to the publisher and to other subscribers. For merge replication, data is synchronized during the merge process when data changes at all servers are converged. Conflicts, if any, are detected and resolved. |
See Also
Copyright © 2005 Microsoft Corporation.
All rights reserved.