Upgrade Guide › Upgrading Databases › Database Upgrade Procedure › SQL Server: Post-Upgrade Table Change

SQL Server: Post-Upgrade Table Change

Only required if upgrading from version 6.0 or earlier.

After upgrading your CMS, you must: back up your CMS database; run a pre-flight check; and finally run a script to modify the participant address columns in the Wgn3EventParticipant table. The full procedure is summarized below:

1. Back up your CMS.
2. Install the required stored procedures into your database.
3. Run a pre-flight check to confirm that the necessary conditions and requirements are met.
4. Prepare to update the table (for example, by restricting database access).
5. Run a ‘table modification’ script.

   In fact, you can either run a single script that performs all the necessary steps or you can run two separate scripts, allowing you to pause the table change at the critical point.

   The actual table changes involve the following steps.

   1. Participant records are copied out of the table to a file.
   2. The table is truncated (which is why you must back up your CMS in step 1)
   3. The participant columns are redefined as mandatory.
   4. Participant records are copied back into the updated table.
6. Back up your CMS again to create a restore point.

Progress is recorded in log files. The following sections describe these stages in detail.