Comments
Sort by recent activity
Hi Jakob, SQL Clone Agents support multiple SQL Server instances running on the same machine. In order for SQL Clone to pick up the new instances, you will need to restart the SQL Clone agent. Detection of SQL Server instances only happens during Agent startup at present. / comments
Hi Jakob,SQL Clone Agents support multiple SQL Server instances running on the same machine. In order for SQL Clone to pick up the new instances, you will need to restart the SQL Clone agent. Detec...
Hi, We made a change in this area in the most recent release to support running builds/releases against different databases than the one they were originally created for. This is useful if you have many databases that should be at in the same state and want to run the same update on all of them. It also aligns workflows that can be done with release artifacts for SQL Change Automation and SQL Source Control projects. For most automation scenarios the database name sqlcmd variable will be set as part of the `Use-ReleaseArtifact` PowerShell cmdlet or as one of the steps in the ReadyRoll AzureDevOps addon. Looking at the code you've provided it looks like you're making use of the package script where these variable definitions are commented out by default. Could you tell us more about your workflow for deployments and what has changed / the issue now experienced in the update? / comments
Hi,We made a change in this area in the most recent release to support running builds/releases against different databases than the one they were originally created for. This is useful if you have ...
Thanks for letting us know. I've just raised a change to get the variable added back in to the package script as I can see why it is annoying to have to manually add this when all the information is available. This will not prevent the script running on other databases if needed. / comments
Thanks for letting us know. I've just raised a change to get the variable added back in to the package script as I can see why it is annoying to have to manually add this when all the information i...
Hi, This article contains examples of how to automate deployments using the PowerShell module: https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments / comments
Hi,This article contains examples of how to automate deployments using the PowerShell module:https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments
We have a number of internal libraries (e.g. The versioning engine and the SQL Compare engine.) that we would have to move first. These are fairly large and would take quite a lot of effort to move. Its something we are interested in doing but is not part of our immediate road map. / comments
We have a number of internal libraries (e.g. The versioning engine and the SQL Compare engine.) that we would have to move first. These are fairly large and would take quite a lot of effort to move...
Hi, Sadly we do not currently support running SQL Change Automation on PowerShell Core. / comments
Hi,Sadly we do not currently support running SQL Change Automation on PowerShell Core.
Hi, We don't currently have support for failing the build if there are pending changes to be imported from the development database. It would be interesting to know more about your use case in case we do any work in this area in the future. / comments
Hi,We don't currently have support for failing the build if there are pending changes to be imported from the development database. It would be interesting to know more about your use case in case ...
Hi, By default VSTS tasks will only show errors, warnings, and the Powershell output stream in the log. We currently write the details of which scripts are being run to the verbose stream so these will not be shown. You can see these log messages by setting `System.debug` to `true` in the variables of your release. We're having some discussion as a team at the moment about increasing the feedback shown by default during the release tasks. / comments
Hi,By default VSTS tasks will only show errors, warnings, and the Powershell output stream in the log. We currently write the details of which scripts are being run to the verbose stream so these w...
Hi, You can disable the user transaction for the migration script by setting the following property at the top of the affected migration. For more details on how SQL Change Automation handles transactions see the article here. <Migration ID="(migration id)" TransactionHandling="Custom" /> Out of interest how was the migration created? The fix mentioned above sets this property automatically if importing a MoT from the development database using the import screen. If the script was created manually or edited after import the Migration header will need to be set manually. / comments
Hi,You can disable the user transaction for the migration script by setting the following property at the top of the affected migration. For more details on how SQL Change Automation handles transa...
The only other header I'm aware of is the "InlineDependencies" option which is used as part of our CLR functionality to bring in external file contents. / comments
The only other header I'm aware of is the "InlineDependencies" option which is used as part of our CLR functionality to bring in external file contents.