After you have upgraded, you will no longer be able to scan any part of the transaction log that existed before the upgrade, so you must follow the following process if your server contains replicated primary databases (this includes replicated RSSDs). This procedure will help to ensure that all replicated data from a replicated database has made it safely to the replicate database.
WARNING! Be sure to have valid dumps of the database and its transaction log before executing the procedures in the follwing sections.
The procedures described here do not upgrade Replication Server itself. For information on upgrading Replication Server, see your Replication Server documentation.
The database upgrade procedure consists of:
Suspending transaction processing and replication activities.
Draining transaction logs for primary databases.
Draining the Replication Server System Database (RSSD) log.
Disabling the log truncation point.
To determine whether your existing server contains replicated databases:
Use isql to connect to the Server you are upgrading.
If your server uses Replication Agent to replicate data, connect to the server and execute:
1> sp_config_rep_agent 2> go
The above command will display the list of databases enabled for replication agent. If you are using other applications to replicate data, LTM or Replicator run the following command in each database (including master databases):
1> dbcc gettrunc 2> go
If the command returns “1” for “secondary trunc state” in any database, replication is enabled in that database.
