Stop replication on the primary database computer

Follow these steps to stop replication on the primary PI AF SQL database computer:

1. Notify users to stop making changes. Make sure replication is completed and all changes are fanned out to secondary servers.

   Note: Any updates that are in progress are likely to be lost. It is recommended that you notify your users ahead of time that they should not attempt to make any changes to the PI AF SQL data during the brief period of time it takes to install the PI AF upgrade.

2. Verify that replication is complete using either of the following techniques:

   • For a simple configuration with one primary and one secondary PI AF SQL database computer:

   1. Open SQL Server Management Studio.

   2. On the primary PI AF SQL database computer, right-click Replication and select Launch Replication Monitor.

   3. Expand Replication Monitor > My Publishers > <Primary Database Server Name>.

   4. Select [<PIFD>]: PIAF, where <PIFD> is the name of the PI AF SQL database.

   5. Select the All Subscriptions tab.

   6. Confirm that the Status is Running and the Last Synchronization time is very recent.

      • For more complex configurations with multiple secondary PI AF SQL database computers:

   7. Open SQL Server Management Studio.

   8. On the primary PI AF SQL database computer, expand Replication > Local Publications > [<PIFD>]: PIAF, where <PIFD> is the name of the PI AF SQL database.

   9. Right-click <Secondary Database Server Name>].[<PIFD>] and select View Synchronization Status.

   10. Confirm that the Status is No replicated transactions are available.

   11. On a secondary PI AF SQL database:

       1. Expand Replication > Local Subscriptions.

       2. Right-click [<PIFD>] - [<Primary Database Server Name>].[<PIFD>]: PIAF and select View Synchronization Status.

       3. Confirm that the Status is No replicated transactions are available.

   12. Repeat the previous step on all of the other secondary PI AF SQL databases.

3. In AF Collective Manager, right-click the AF Collective and select Properties.

4. Select the Collective tab.

5. Right-click the primary server and select Stop Replication.

   Replication is stopped on the primary server and all secondary servers. As long as the collective still exists, you can start replication on the primary server at a later time; you will need to start replication on each secondary server, too.