Comments
Sort by recent activity
Hi Brujah,
We have just released DLM Automation 2 which contains SQL Compare 12. You can download it as part of the SQL Toolbelt - http://www.red-gate.com/dynamic/product ... t/download / comments
Hi Brujah,
We have just released DLM Automation 2 which contains SQL Compare 12. You can download it as part of the SQL Toolbelt - http://www.red-gate.com/dynamic/product ... t/download
Hi Mattias,
Apologies for making another change. We've trying to simplify our DLM offering and that included making it all one tool instead of several. There are no further changes planned for the DLM Tools and you can continue with your current setup just fine.
If you are using a plugin you don't need to make any changes, and if you are using the command line it will still be available but won't be worked on. If your current builds are working then you can continue to use SQL CI without any problems.
Peter / comments
Hi Mattias,
Apologies for making another change. We've trying to simplify our DLM offering and that included making it all one tool instead of several. There are no further changes planned for the ...
Hi,
SQL Release will always drop tables if they aren't being source controlled. But you do have some ways to stop it.
The simplest way is to add a filter that ignores the tables that are being dropped (https://documentation.red-gate.com/disp ... QL+Release), this works if the tables that are being dropped are always the same ones.
Alternatively you can check all tables into Source Control.
You can add a manual review step or interrogate the warnings with powershell and stop if there is a table drop:
$ErrorActionPreference = "Stop"
$db = New-DlmDatabaseConnection -ServerInstance .sql2012 -Database northwind
$scripts = "C:Northwind"
$release = New-DlmDatabaseRelease -Source $scripts -Target $db
if ($release.Warnings.Details -match "The table S* is being dropped") {
throw "Table being dropped"
}
If you mean you want to rename instead of Drop/create you can use Migrations for this https://documentation.red-gate.com/disp ... on+scripts
Peter Gerrard Developer - DLM Automation / comments
Hi,
SQL Release will always drop tables if they aren't being source controlled. But you do have some ways to stop it.
The simplest way is to add a filter that ignores the tables that are being drop...
Hi Mark,
Unfortunately SQL Release does not work with Migrations v1. We are currently working on improving Migrations and getting them to work with SQL CI and SQL Release, this should be done by the end of the month. The beta has finished and is almost ready for release. For more information check out: https://documentation.red-gate.com/disp ... ease+notes https://documentation.red-gate.com/disp ... on+scripts
Also as you correctly point out it needs to point at the Database folder rather than its parent to work with filters and static data, this should be done at build time (sqlci build or Invoke-DlmDatabaseSchemaValidation) / comments
Hi Mark,
Unfortunately SQL Release does not work with Migrations v1. We are currently working on improving Migrations and getting them to work with SQL CI and SQL Release, this should be done by th...
Hi,
We have just released the latest version of SQL Release to the VSTS plugin. This includes SQL Compare 11.5.2 which fixes the Azure v12 issue. / comments
Hi,
We have just released the latest version of SQL Release to the VSTS plugin. This includes SQL Compare 11.5.2 which fixes the Azure v12 issue.
Have you restarted the tentacle since installing SQL Release? This needs to be done as the tentacle won't have picked up the install. / comments
Have you restarted the tentacle since installing SQL Release? This needs to be done as the tentacle won't have picked up the install.
Just as an update, we have fixed this issue as of today's release (3rd June) in version 1.2.1.2643
When you press Ctrl-C during parameter prompt you should no longer get any extra output and be on a fresh prompt. / comments
Just as an update, we have fixed this issue as of today's release (3rd June) in version 1.2.1.2643
When you press Ctrl-C during parameter prompt you should no longer get any extra output and be on ...
Hi Iain,
I've just repeated this and appear to have reproduced it:
PS C:UsersPeter.Gerrard> New-DatabaseConnection
cmdlet New-DatabaseConnection at command pipeline position 1
Supply values for the following parameters:
ServerInstance:
PS C:UsersPeter.Gerrard> New-DatabaseConnection, SQL Release 1.2.0.2364, Copyright © Red Gate Software Ltd 2014-2015
Though it does not appear to hang for me, pressing return gives me a fresh prompt or I can just type my command in again. Which suggests to me it is a visual bug, which I will raise with the rest of the team. Could you try pressing return to see if this fixes it, please let me know either way. / comments
Hi Iain,
I've just repeated this and appear to have reproduced it:
PS C:UsersPeter.Gerrard> New-DatabaseConnection
cmdlet New-DatabaseConnection at command pipeline position 1
Supply values for ...
Hi Alanna,
Your error tells me that the $targetDB is not the same as the -Target parameter of New-DatabaseRelease. There are a number of reasons this could be:
The source and target parameters have been mixed up (Source should be Test_A and Target is Test_B)
Unlikely - Test_B has been changed between creating the release and using it
A bug in SQL Release
To help Diagnose the problem could you please send us the script you are using and the log with the debug output. To get the debug output at the top of your script add the line:
$DebugPreference = "Continue"
If you don't want to post these to a public forum, could you send them to us at SQLReleaseSupport@red-gate.com / comments
Hi Alanna,
Your error tells me that the $targetDB is not the same as the -Target parameter of New-DatabaseRelease. There are a number of reasons this could be:
The source and target parameters hav...
Hi Paul,
We don't support full connection strings in SQL Release, we only support those parts we support through the New-DatabaseConnection cmdlet - Server, DataSource, IntegratedSecurity, UserId, Password. If you want us to support any other connection string properties then please put in a feature request on our uservoice.
If you need to run the script then you can export the script to a file then run it through your preferred way of running scripts:
$databaseUpdate.UpdateSql | Out-File <Path>Update.sql
I hope this helps, / comments
Hi Paul,
We don't support full connection strings in SQL Release, we only support those parts we support through the New-DatabaseConnection cmdlet - Server, DataSource, IntegratedSecurity, UserId, ...