Comments
Sort by recent activity
Thanks, I'll try that. That said, it would be nice to be able to set this option from the cmdlet, there are certain environments where I'm OK with potential data loss, and others where I'm not [image] / comments
Thanks, I'll try that. That said, it would be nice to be able to set this option from the cmdlet, there are certain environments where I'm OK with potential data loss, and others where I'm not
Hi Jack, Thanks for the information and workaround suggestion. I'll be able to use the workaround during the development phase, but we'll definitely need to use the bulk insert strategy as we move towards production in the coming months. Just so I can plan ahead, is there a plan/timeline for when this bug might be fixed?
/ comments
Hi Jack,Thanks for the information and workaround suggestion. I'll be able to use the workaround during the development phase, but we'll definitely need to use the bulk insert strategy as we move ...
Hi Diogo, thanks for that information, Use-DatabaseReleaseArtifact worked much better.
Thanks for your help!
/ comments
Hi Diogo, thanks for that information, Use-DatabaseReleaseArtifact worked much better.
Thanks for your help!
Hi @Diogo do you mean that I should include the .sqlproj filename in my $project variable? Basically, the way this is laid out on the filesystem is: - Solution root folder - [powershell script] - Redgate.Sca.FromExistingDb [folder for SCA project]
- DbArtifacts [root folder for build/release artifacts] - Build - Release
...etc... So normally, when I execute the Powershell script from the root folder, $project resolves to something like: c:\path\to\solution\root\Redgate.Sca.FromExistingDb I'm asking because the examples I've seen all seem to point to the folder containing the .sqlproj rather than the .sqlproj file itself. Any clarification you can provide will be greatly appreciated. PS: The script does successfully build the .sqlproj Build artifacts, I can open the .nuget package and see my migration scripts, etc. The issue is that the Release artifact indicates that there are no changes to be made to the target database even though the source and target aren't in sync.
/ comments
Hi @Diogo do you mean that I should include the .sqlproj filename in my $project variable? Basically, the way this is laid out on the filesystem is:- Solution root folder - [powershell script] -...
Hi @Diogo Thanks for that last hint, I had overlooked the distinction between passing a folder (for Sql Source Control) vs. passing a .sqlproj for SCA. / comments
Hi @Diogo Thanks for that last hint, I had overlooked the distinction between passing a folder (for Sql Source Control) vs. passing a .sqlproj for SCA.