Use the nonatomic bulk materialization procedure

Log in to the replicate Replication Server as the system administrator (sa) using isql:

isql -Usa -Psa_password -SRRS_servername

where:

• sa is the system administrator user ID.

• sa_password is the password for the system administrator user ID.

• RRS_servername is the name of the replicate Replication Server.

Turn on the auto-correction feature at the replicate Replication Server:

1> set autocorrection on
2> for replication_definition
3> with replicate at dataserver.database
4> go

Define the subscription at the replicate Replication Server:

1> define subscription subscription_name
2> for replication_definition
3> with replicate at dataserver.database
4> with suspension
5> go 

The dataserver.database name must match the name you used for your replicate database.

In the primary database, invoke the rs_marker stored procedure to activate the subscription.

Check the subscription at both the primary and replicate Replication Servers. Use the following command to verify that the subscription status is ACTIVE:

1> check subscription subscription_name
2> for replication_definition
3> with replicate at dataserver.database
4> go 

When the subscription status is ACTIVE at the replicate Replication Server, the database connection for the replicate database is suspended.

Unload the subscription data at the primary site using the preferred database unload method for your site to select or dump the data from the primary tables.

In the primary database, invoke the rs_marker stored procedure to validate the subscription.

Wait for the subscription to become valid at both the primary and replicate Replication Servers, then execute the check subscription command at both the primary and replicate Replication Servers to verify that the status is VALID.

Load the subscription data into the replicate database using the bcp utility or the preferred database load utility for your site.

From the replicate Replication Server, resume the database connection for the replicate database:

1> resume connection
2> to dataserver.database
3> go

Wait for the subscription to become valid at both the primary and replicate Replication Servers, then execute the check subscription command at both the primary and replicate Replication Servers to verify that the status is VALID.

When the subscription status is VALID at the replicate Replication Server, the replicate database is synchronized with the primary database and you can turn off auto-correction.