Upgrade Guide › Upgrading Databases › Database Upgrade Procedure › SQL Server: Post-Upgrade Table Change › Run the Pre-Flight Check

Run the Pre-Flight Check

Before you actually update the Wgn3EventParticipant table, you must run a further pre‑flight check script to estimate how long the table updates will take and to check that the necessary system conditions are in place. In particular, it tests whether there is sufficient free disk space in the target directory.

The time estimate is based on a sample of one million table rows. Using the bcp utility, the pre-flight check script copies a maximum of one million rows from the table to the file system, measuring the time and disk space required to do so. Using these figures, it then calculates the disk space required to copy out the entire table and estimates how long this will take.

1. The pre-flight check is implemented as a stored procedure (SP), contained in the following file:

   wgn_post_upgrade_pfc.sql
   

   1. Find this file in the following folder in your CA DLP distribution media:

      \Support\Upgrade12\MSSQL

   2. Open and execute this file In SQL Server Management Studio in order to create the SP.
   3. Run the following command as a login with the sysadmin role (for example, sa). Note that you must use the same login when you actually modify the table (see step 1 in section 5, Run the Modify Table Script).

      EXEC wgn_post_upgrade_pfc '<dir>'
      

      where <dir> is the target folder where participant records will be copied to. You must specify a folder on the database host server (this is not necessarily the same as the CMS host server). This folder must already exist. For example:

      EXEC wgn_post_upgrade_pfc 'C:\MyDir'
      

      Note also:

      • For performance reasons, we strongly recommend that this directory is on a separate disk from the actual database.
      • You must specify the same target directory for the pre-flight check and the actual table update. This ensures that the time estimate and disk space check are meaningful.
      • Do not include a trailing backslash.
2. Check the script output in the Messages tab in SQL Server Management Studio. This output indicates whether the necessary conditions have been met and estimates the time needed to update the table. In particular, the script output:
   • Confirms whether the AddressUID columns are currently defined as NULL.
   • Confirms whether the xp_cmdshell feature is enabled and the specified login has permission to use it. The table modification script will use this feature to run bcp commands when copying participant records between the database and the target directory.
   • Shows the actual bcp command used by the pre‑flight check to copy table records to the target directory. To help diagnose problems, the bcp output is also piped to a log file, bcp_pf_ep_data.log.
   • Indicates whether there is sufficient free disk space in the target directory to store all the participant records.
   • Estimates how long the entire procedure will take to modify the Wgn3EventParticipant table.
3. You can now prepare to update the table.

More information:

Run the Modify Table Script

Example Pre-Flight Check Output

Prepare to Modify the Table