Upgrade Guide › Upgrading Databases › Database Upgrade Procedure › SQL Server: Post-Upgrade Table Change › Back Up Your CMS Database Again

Previous Topic: Run the Modify Table Script

Next Topic: Monitoring the Progress of Table Changes
Back Up Your CMS Database Again

The table update is now complete. As a final step in the overall procedure, you now need to back up your CMS database again to create a new restore point.

This is not just good practice. It is an essential precautionary step because, while the table was being repopulated (see step 7 in section 5, Run the Modify Table Script), the database recovery model was set to BULK_LOGGED mode. Consequently, the changes to the participant records were not logged. This means that any table backups predating the post-upgrade changes to the participant address columns will not be usable if you need to restore the table in the future.