Upgrade Guide › Upgrading Databases › Upgrading a 6.0 Database › SQL Server: Post-Upgrade Change To Event Participant Table

SQL Server: Post-Upgrade Change To Event Participant Table

(Only required if upgrading from version 6.0)

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

How to Implement the Post-Upgrade Table Change

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

   You can run a single script that performs all the necessary steps, or you can run two separate scripts.

   Running two scripts allows you to check that preparations completed successfully before you truncate the table. (The bcp export log and script output indicate if any problems occurred during the preparations.)

   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. This is why you must back up your CMS in step 2.
   3. The participant columns are redefined as mandatory.
   4. Participant records are copied back into the updated table.
6. Monitor the progress of table changes and confirm that the script has completed successfully. Progress is recorded in log files.
7. Verify that the table changes completed successfully.
8. Back up your CMS again to create a restore point.

These steps are described in the following sections.