Log in to the replicate Replication Server as the System Administrator (sa) using isql:
isql -Usa -Psa_password -Sservername
Issue the Replication Server define subscription command at the replicate Replication Server using the following syntax:
define subscription subscription_name for replication_definition with replicate at dataserver.database [where search_conditions]
Check the subscription at both the primary and replicate Replication Servers to verify that the subscription status is DEFINED. Use the following syntax:
check subscription subscription_name for replication_definition with replicate at dataserver.database
Activate the subscription, using the with suspension clause, at the replicate Replication Server. Use the following syntax:
activate subscription subscription_name for replication_definition with replicate at dataserver.database with suspension
Wait for the subscription to become active at the primary Replication Server and any replicate Replication Servers; then, execute the Replication Server check subscription command at the primary and replicate Replication Servers to verify that the subscription status is ACTIVE.
When the subscription status is ACTIVE at the replicate Replication Server, the database connection for the replicate database is suspended.
As soon as the subscription becomes active at the primary Replication Server, retrieve the data from the primary database using your site’s preferred database unload method.
Validate the subscription at the replicate Replication Server using the following syntax:
validate subscription subscription_name for replication_definition with replicate at dataserver.database
Load the subscription data from the media into the replicate database.
From the replicate Replication Server, enable autocorrection for the replication definition at the replicate database using the following syntax:
set autocorrection on for replication_definition with replicate at dataserver.database
From the replicate Replication Server, issue the Replication Server resume connection command to restore the connection to the replicate database using the following syntax:
resume connection to dataserver.database
Wait for the subscription to become valid at both the primary and replicate Replication Servers; then issue the Replication Server check subscription command at the primary and replicate Replication Servers to verify that the subscription status is valid.
When the subscription status is valid, the replicate data is consistent with the primary data.
From the replicate Replication Server, turn autocorrection off for the replicate database using the following syntax:
set autocorrection off for replication_definition with replicate at dataserver.database
Now the subscription is created and replication is active.
