Introduction
Migrating from SQL Source Control to VersionSQL is a straightforward process. The steps outlined here will guide you through connecting your database, reviewing scripting engine differences, committing a new baseline, and viewing your complete commit history.
Connecting Database
- Install VersionSQL and Open SQL Server Management Studio.
- Select the database that was managed by SQL Source Control.
- Right-click on it and select ‘Connect to Version Control’.
- Paste in the repository URL and click OK.
- Click “Yes” to begin scanning your database.
Reviewing Scripts
Once scanning is complete, you’ll be presented with a list of objects that have differences between the database and the repository. This is due to VersionSQL and SQL Source Control having slightly different scripting engines. Double-click on each object to review the differences.
Committing Baseline
When you’re ready to proceed, type a log message and click OK to proceed. VersionSQL will commit these formatting changes to your repository. From now on, only new changes to your database objects will be shown when you start a commit.
Viewing History
To view the database’s change history, right-click the database and select ‘View History’. Notice that Redgate SQL Source Control commits are present, as well as those made using VersionSQL. Your complete database change history has been preserved.
Conclusion
This has been a quick overview of how to migrate your existing SQL Source Control database version control solution to VersionSQL. Thank you for considering VersionSQL for your database version control needs!
If you have any questions about whether VersionSQL is right for you, or need help getting started, please reach out to me via [email protected].