Historical migration scripts
Published 13 May 2016
A historical migration script covers changes you've already committed.
You can add a historical migration script using your version control system:
In your version control system:
- Checkout the revision prior to the changes that required a migration script.
- Create a new branch (eg Historical migration).
In SQL Source Control, switch to the new branch.
The working database in SQL Source Control is reverted to the revision selected in step 1a.- Make the changes that required a migration script.
- Create a new migration script.
- Commit the migration script.
- In your version control system, merge the new branch into master.
Deploying from the latest revision now executes the new migration script at the correct point.
This documentation contains proprietary information and is protected by copyright law.
Copyright © 2026 Red Gate Software Limited. All rights reserved