Comments
Sort by recent activity
It would be great to see some scripts that might go set up a new pipeline for a hotfix, maybe grab a release branch or commit tag and set up a quick way to release a patch. / comments
It would be great to see some scripts that might go set up a new pipeline for a hotfix, maybe grab a release branch or commit tag and set up a quick way to release a patch.
AFAIK, We don't populate the Projects section there. All of what SCA tracks/manages is in the Solution Explorer, with a table view shown in the Offline Schema Explorer. This is just for viewing, as changes are made through the migration scripts. / comments
AFAIK, We don't populate the Projects section there. All of what SCA tracks/manages is in the Solution Explorer, with a table view shown in the Offline Schema Explorer. This is just for viewing, as...
Likely a bug then. / comments
Likely a bug then.
It's hard to know what is going on without the db and project (and vcs repo). SCA-VS uses SQL Compare to generate the differences for the Import pane. You shouldn't ever compare or change the Shadow db. That's for the tool to verify some script changes. You should only be detecting differences between your VCS repo/project and the development db. If there aren't any changes, can you repro this at all? Any ideas? Or can you zip up the repo and a backup of the db and post? / comments
It's hard to know what is going on without the db and project (and vcs repo). SCA-VS uses SQL Compare to generate the differences for the Import pane.You shouldn't ever compare or change the Shadow...
This isn't against the shadow database. The change is detected between the development database and the project. That's where things change. The Shadow is used to verify the script works after being imported and syncs shadow from the previous version of the project to the latest version. / comments
This isn't against the shadow database. The change is detected between the development database and the project. That's where things change. The Shadow is used to verify the script works after bein...
How have you configured the task for build? Are you entering a database name? / comments
How have you configured the task for build? Are you entering a database name?
The script does not do anything with logins. However, if does try to create users with matching login names. A login can only be mapped to one user in a database. This makes me wonder if you are trying to verify a deployment script against a target that has a login already mapped. Do you have logins mapped to different user names? / comments
The script does not do anything with logins. However, if does try to create users with matching login names. A login can only be mapped to one user in a database. This makes me wonder if you are tr...
I tend to leave the first script (001) as the baseline and letting the system detect this. It's supposed to detect if the target (prod) has the objects. However, this is where you try to get prod synced with a baseline first and then start adding objects to dev that are added to the project separately. I'm not 100% sure how the <skipbaselinecheck> affects this, so let me ask someone else / comments
I tend to leave the first script (001) as the baseline and letting the system detect this. It's supposed to detect if the target (prod) has the objects. However, this is where you try to get prod ...
Glad that you're making progress. Baby steps is the best way, and thank you for the very kind words. / comments
Glad that you're making progress. Baby steps is the best way, and thank you for the very kind words.
You can pull out the script to create those objects from your baseline script. Once those are in prod, you can give the update.SQL script from the create release step to the DBAs to review and run manually. This will update the migration log as part of the script until you implement more automation / comments
You can pull out the script to create those objects from your baseline script. Once those are in prod, you can give the update.SQL script from the create release step to the DBAs to review and run ...