Comments
Sort by recent activity
Yes I have been using this documentation as I've been working through this migration.
I can confirm I committed the migration script before doing any deployment using SQL Compare. However after this step I am confused as to what should happen.
You mentioned I should commit the NOT NULL constraint change to the column after the migration script. Do I need to make another script to do this? I ask this because I assumed when I was comparing my out of date DB, the deployment script that gets generated was going to do this, which when glancing over the script, it does.
For sanity's sake I started from the beginning, created a copy of my DB to be migrated.
- I linked the DB to a source control (in this case I just linked it to a local folder).
- I immediately commit the schema changes to the source control this time
- I create a blank script for the actually migration for the table that needs the NOT NULL and commit it
At this point I am confused, do I need another migration script to make the NOT NULL change?
I do the SQL Compare and select the table that needs the NOT NULL. As soon as I do, the compare SQL Compare gives me a warning that migration scripts won't be run at the top of the window. Sure enough, the deployment fails. / comments
Yes I have been using this documentation as I've been working through this migration.
I can confirm I committed the migration script before doing any deployment using SQL Compare. However after thi...