Comments
Sort by recent activity
Russell D said:
Hi Peter, this could be a problem with the syntax - can you share the command you're trying?
Russel - I put this code in the thread. Hoping you can shed some light on correct usage. / comments
Russell D said:
Hi Peter, this could be a problem with the syntax - can you share the command you're trying?
Russel - I put this code in the thread. Hoping you can shed some light on correct...
Just to be clear, I'm hearing you say that the recommendation is to NOT use the MSBuild when we have full version of SCA in VS. For full version of SCA, we should use the CI add-ons? What about scripting with the PC cmdlets? I'm guessing you mean that we use those, too - not JUST the CI add-ons (e.g. for Bamboo). It's late in the day -I'm not having an easy time expressing myself here... / comments
Just to be clear, I'm hearing you say that the recommendation is to NOT use the MSBuild when we have full version of SCA in VS. For full version of SCA, we should use the CI add-ons? What about sc...
It's also not generated when deploying using MSBuild within the IDE. / comments
It's also not generated when deploying using MSBuild within the IDE.
Thank you, Sergio. I realize it's a low priority request that may sit in the sprint backlog. / comments
Thank you, Sergio. I realize it's a low priority request that may sit in the sprint backlog.
Sergio answered the question, but for additional documentation, the schema snapshot will NOT get created when deploying using SSMS (ie TargetedDeploymentScript.sql). / comments
Sergio answered the question, but for additional documentation, the schema snapshot will NOT get created when deploying using SSMS (ie TargetedDeploymentScript.sql).
# And here is the code that exported the build artifact $ErrorActionPreference = "stop" # Input path to SCA project file $pathToProjectFile = "C:\Users\peter\Documents\IncommSVN_PPD\SCAPOC\SCAPOC\SCAPOC\SCAPOC.sqlproj" #validate the project by building $validatedProject = $pathToProjectFile | Invoke-DatabaseBuild #create athe build artifcat and export it to file $buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId "SCAPOC" -PackageVersion 1.0.0 $buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\DatabaseBuild\" -Force / comments
# And here is the code that exported the build artifact$ErrorActionPreference = "stop"# Input path to SCA project file$pathToProjectFile = "C:\Users\peter\Documents\IncommSVN_PPD\SCAPOC\SCAPOC\SCAP...
$ErrorActionPreference = "stop" #Input the build artifact nupkg file path $pathToBuildArtifact = "C:\Export\DatabaseBuild\SCAPOC.1.0.0.nupkg" #Input the path to export the release artifact to $exportPath = "C:\Export\DatabaseRelease\tmp" #try multiple targets $t1 = New-DatabaseConnection -ServerInstance "localhost" -Database "SCAPOC_UAT" $t2 = New-DatabaseConnection -ServerInstance "localhost" -Database "SCAPOC_PROD" #ERROR: To create a release for a SQL Change Automation project, the Target parameter must be a single Database #Connection. #Create and export a release artifact - based on 2 targets $releaseArtifact = New-DatabaseReleaseArtifact -Source $pathToBuildArtifact -Target @($t1, $t2) / comments
$ErrorActionPreference = "stop"#Input the build artifact nupkg file path$pathToBuildArtifact = "C:\Export\DatabaseBuild\SCAPOC.1.0.0.nupkg"#Input the path to export the release artifact to$exportPa...
Excellent! And thanks for updating the online docs. I'm really enjoying how responsive the RG team has been. I think your'e right - File Path ordering might be appropriate for this situation. As a supporting "Dev DBA", I don't want to impact the dev team's traditional sprint/release naming convention (much) at this point. / comments
Excellent! And thanks for updating the online docs. I'm really enjoying how responsive the RG team has been. I think your'e right - File Path ordering might be appropriate for this situation. As...
Thanks, Alex. So, I see that page under the "SQL Automation Core". I guess I assumed that it was not applicable to the case where I'm using the SCA "full tooling" and the PS cmdlets. I'm getting the sense that I should look at both folders of documentation to get a full picture. Correct? / comments
Thanks, Alex. So, I see that page under the "SQL Automation Core". I guess I assumed that it was not applicable to the case where I'm using the SCA "full tooling" and the PS cmdlets. I'm getting...
How do you normally connect to this database? Are you able to connect to it using other tools (e.g. SSMS, sqlcmd) using integrated security from this host? Or do you need to use a SQL login? / comments
How do you normally connect to this database? Are you able to connect to it using other tools (e.g. SSMS, sqlcmd) using integrated security from this host? Or do you need to use a SQL login?