Upgrade Guide › Upgrading Databases › Upgrading a 6.0 Database › How to Upgrade a 6.0 Database › 3. Modify the Event Participant Table

3. Modify the Event Participant Table

After upgrading the CMS, the AddressUID columns in the Wgn3EventParticipant database table must be redefined as NOT NULL. This ensures that email addresses are mandatory for participants in this database table. You must make this table change manually on the CMS (for gateways and other CA DataMinder servers, the table is modified automatically as part of the r12.0 upgrade).

• For Oracle CMSs, this is a simple schema change. Before you run the table update script, we recommend that you run a further pre‑flight check script to estimate how long the table updates will take.
• For SQL Server, the process is more complicated. This is necessary for performance reasons. Our testing revealed that, paradoxically, a simple schema change such as that implemented for Oracle databases could be unacceptably slow and consume excessive disk space (for log files) when applied to very large SQL Server tables.

  Before you run the table update script, you must run a further pre‑flight check script to check that the necessary system conditions are in place and to estimate how long the table updates will take and how much free disk space is required.

More information:

Oracle: Post-Upgrade Change To Event Participant Table

SQL Server: Post-Upgrade Change To Event Participant Table