Comments
Sort by recent activity
Decided to bite the bullet and 1. force uninstalled the existing VC++ 2017 runtime 2. installed SQL Clone Agent 3. re-installed VC++ 2017 package in Chocolatey At first glance everything appears to be ok. / comments
Decided to bite the bullet and 1. force uninstalled the existing VC++ 2017 runtime2. installed SQL Clone Agent3. re-installed VC++ 2017 package in ChocolateyAt first glance everything appears to be...
For future visitors here: Following the link to PS Cmdlets I ended up with this, which demonstrates the concept. The first script builds a nuget package from your SQL Source Control scripts # Path to SQL Source Control scripts
$project = "C:\dev\Sandbox\MyDbProject\"
$validatedProject = $project | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.1.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\dev\Sandbox\MyDbProject\"And this one deploys nuget package built in previous step to target db $buildArtifactPath = "C:\dev\Sandbox\MyDbProject\MyDatabase.1.1.0.nupkg"
$buildArtifact = $buildArtifactPath | Import-DatabaseBuildArtifact
# The below line uses windows authentication, if you want to connect with SQL user append these params: -Username "user" -Password "pwd"
$production = New-DatabaseConnection -ServerInstance "." -Database "DeployDB"
$update = New-DatabaseReleaseArtifact -Source $buildArtifact -Target $production
Use-DatabaseReleaseArtifact $update -DeployTo $production / comments
For future visitors here:Following the link to PS Cmdlets I ended up with this, which demonstrates the concept.The first script builds a nuget package from your SQL Source Control scripts# Path to ...
Thanks Alex. That was the info I was looking for [image] / comments
Thanks Alex. That was the info I was looking for