Activity overview
Latest activity by CopperStarSystems
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
How to set DriftOptionBlockDataLoss when using Powershell cmdlets
We are using the Sql Change Automation Powershell cmdlets in our build/release pipeline on a VSTS Hosted VS2017 agent.We have a recent commit that drops a column from an existing table, however whe...
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 ...
Bulk import error when deploying database using Use-DatabaseReleaseArtifact cmdlet
I have a project that needs to have certain static data seeded when deploying to a new database instance.
Following the guidance at https://documentation.red-gate.com/sca3/developing-databases-us...
Bulk import error when deploying database using Use-DatabaseReleaseArtifact cmdlet
I have a project that needs to have certain static data seeded when deploying to a new database instance.
Following the guidance at https://documentation.red-gate.com/sca3/developing-databases-us...
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!
Error deploying a Sql Change Automation Build Artifact using Sync-DatabaseSchema cmdlet
I'm in the process of configuring a Powershell CI/CD pipeline using the RedGate cmdlets.
Everything appears to be functioning correctly until I get to the Sync-DatabaseSchema step, which fails wi...
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.
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] -...