Comments
Sort by recent activity
Hi,
You can replace the default scripts by using the Migrations feature in SQL Source Control.
Please see below for more information: http://documentation.red-gate.com/displ ... on+scripts
Thank you, / comments
Hi,
You can replace the default scripts by using the Migrations feature in SQL Source Control.
Please see below for more information:http://documentation.red-gate.com/displ ... on+scripts
Thank you,
Hi,
I am sorry that you are having issues when using SQL Source Control.
We have introduced caching in the latest versions of SQL Source Control, in some cases and since the tool runs within SSMS.exe which a 32bit process and therefore limited in the amount of RAM it can access this can cause out of memory exceptions.
To avoid this issue you should disable caching by following these steps:
1 - You need to have Frequent Updates turned on http://documentation.red-gate.com/displ ... nt+Updates
2 - Update to the latest Frequent Update (version 4.2.1)
3 - After updating you will need to edit the following file:
%localappdata%Red GateSQL Source Control 4RedGate_SQLSourceControl_Engine_EngineOptions.xml
and add the following:
<EngineOptions version="3" type="EngineOptions">
<DisableCaching>True</DisableCaching>
</EngineOptions>
(Please note that %localappdata% usually corresponds to `C:Users(username under which SSMS runs - usually the logged in user)AppDataLocal)
Thank you, / comments
Hi,
I am sorry that you are having issues when using SQL Source Control.
We have introduced caching in the latest versions of SQL Source Control, in some cases and since the tool runs within SSMS.e...
Hi RofL,
The DLM tool used with the Team City plugin is SQL CI.
You should install the latest version of that tool.
Thank you, / comments
Hi RofL,
The DLM tool used with the Team City plugin is SQL CI.
You should install the latest version of that tool.
Thank you,
Hi Rofl,
I have created a support incident so that we can troubleshoot further, as I believe this might be something specific to your environment.
The DLM Automation Tool has been upgraded to a SQL Compare engine in which this issue has been fixed.
Thank you, / comments
Hi Rofl,
I have created a support incident so that we can troubleshoot further, as I believe this might be something specific to your environment.
The DLM Automation Tool has been upgraded to a SQL...
Hi RofL,
In your case you should make sure that you have the latest DLM Automation Suite version installed.
Thank you, / comments
Hi RofL,
In your case you should make sure that you have the latest DLM Automation Suite version installed.
Thank you,
Hi,
This issue has now been fixed in SQL Source Control 4.2.3, which is available on the Frequent Updates channel.
Thank you, / comments
Hi,
This issue has now been fixed in SQL Source Control 4.2.3, which is available on the Frequent Updates channel.
Thank you,
Hi Frederic,
Thanks for your post.
You need to enable the Use case-sensitive object definition database comparison option.
Please see below how to change the Comparison options: http://documentation.red-gate.com/displ ... on+options
I hope this helps.
Thank you, / comments
Hi Frederic,
Thanks for your post.
You need to enable the Use case-sensitive object definition database comparison option.
Please see below how to change the Comparison options:http://documentation...
Hi,
I am sorry that you are having issues when using SQL Source Control.
Please try the following:
GRANT ALTER TRACE TO <user> https://msdn.microsoft.com/en-us/library/cc293611.aspx
Also make sure that you have the user permissions set as per the following document: http://documentation.red-gate.com/displ ... ermissions
Thank you, / comments
Hi,
I am sorry that you are having issues when using SQL Source Control.
Please try the following:
GRANT ALTER TRACE TO <user>https://msdn.microsoft.com/en-us/library/cc293611.aspx
Also make sure t...
Hi,
I am afraid that this is by design: schema name should be unique within a pipeline and since it is possible to move schemas between pipelines they need to be unique globally.
I suggest you use a unique prefix to each database, for example: DB1 - version 1.3 and DB 2 - version 1.3
Thank you, / comments
Hi,
I am afraid that this is by design: schema name should be unique within a pipeline and since it is possible to move schemas between pipelines they need to be unique globally.
I suggest you use ...
Hi Andrew,
I am afraid that this appears to be caused by a bug, which we are investigating at the moment.
We have opened a support ticket for this issue and I will get back to you on that ticket soon.
Thank you, / comments
Hi Andrew,
I am afraid that this appears to be caused by a bug, which we are investigating at the moment.
We have opened a support ticket for this issue and I will get back to you on that ticket so...