Comments
Sort by recent activity
Glad it's fixed. Apologies for the difficulty in working it out. I'll make sure your comment about the error code is passed on. / comments
Glad it's fixed. Apologies for the difficulty in working it out. I'll make sure your comment about the error code is passed on.
Hi Steve,
It's available on Frequent Updates: https://documentation.red-gate.com/soc6/installing-licensing-and-updating/update/configuring-frequent-updates / comments
Hi Steve,
It's available on Frequent Updates: https://documentation.red-gate.com/soc6/installing-licensing-and-updating/update/configuring-frequent-updates
Hi madnik,
to help diagnose this we would need some more info from you. I will ask support to get in touch with you. / comments
Hi madnik,
to help diagnose this we would need some more info from you. I will ask support to get in touch with you.
Hi zippy,
it is possible but not officially supported by our installer, and is not on our immediate roadmap to fix this.
Note you have to do this everytime you update SQL Source Control.
- Delete this folder
C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Extensions\SQLSourceControl
This will uninstall from SSMS 17 / comments
Hi zippy,
it is possible but not officially supported by our installer, and is not on our immediate roadmap to fix this.
Note you have to do this everytime you update SQL Source Control.
- Delete t...
Hi,
DLM Automation just uses standard connections, the issue is likely to be in your network setup rather than the SQL Server permission.
To handle connections from VSTS you will need to do one of the following:
Running on VSTS hosted agents
- Ensure you can connect to those servers from a remote agent living in Microsoft Azure. You will need to fully qualify the server you are connecting to, and ensure the firewall is set up to allow these communications.
Running on local VSTS agents
- Ensure you can connect to the server from the machine running the VSTS agent.
For more information on local vs hosted see https://docs.microsoft.com/en-us/vsts/build-release/concepts/agents/agents / comments
Hi,
DLM Automation just uses standard connections, the issue is likely to be in your network setup rather than the SQL Server permission.
To handle connections from VSTS you will need to do one of ...
Hi,
This is intended behaviour. To get into a new version of SSMS you will need to uninstall and install again. Or you can download a later version (we have several frequent releases since 5.7) and update to that. / comments
Hi,
This is intended behaviour. To get into a new version of SSMS you will need to uninstall and install again. Or you can download a later version (we have several frequent releases since 5.7) and...
You can turn on Frequent Updates in SSMS 16: https://documentation.red-gate.com/soc5/installing-licensing-and-updating/update/configuring-frequent-updates/configuring-frequent-updates-in-version-5-4-and-above / comments
You can turn on Frequent Updates in SSMS 16: https://documentation.red-gate.com/soc5/installing-licensing-and-updating/update/configuring-frequent-updates/configuring-frequent-updates-in-version-5-...
Hi,
Your issue is you are doing a data only migration instead of a schema change migration. When you go to the Migrations tab you want to select the table in the "Replace uncommitted schema changes" instead of "Start with blank script" [image]
Then the table will appear under the migration script, and will not show any warnings. / comments
Hi,
Your issue is you are doing a data only migration instead of a schema change migration. When you go to the Migrations tab you want to select the table in the "Replace uncommitted schema changes...
You have two options.
Wait until we release a new version (you already have the latest installed, 5.8.3), this will install into SSMS 2016 and SSMS 17.2
Uninstall SQL Source Control, then run the installer I linked to earlier. This will install into SSMS 2016 and SSMS 17.2
They will both use the same configuration, stored in %LOCALAPPDATA%\Red Gate\SQL Source Control 5 / comments
You have two options.
Wait until we release a new version (you already have the latest installed, 5.8.3), this will install into SSMS 2016 and SSMS 17.2
Uninstall SQL Source Control, then run the ...
It should do so long as SSMS 17.2 is already installed on that machine. / comments
It should do so long as SSMS 17.2 is already installed on that machine.