Comments
Sort by recent activity
Hi Len,
If you have a backup of both the original state and the current state and want to keep both in Source Control, you could:
1- Restore original state
2- Link DB to Source Control
3- Commit original state to Source Control
4- Restore current state
5- Commit current state to Source Control
Your Version Control System should now contain both versions of the DB
Thank you, / comments
Hi Len,
If you have a backup of both the original state and the current state and want to keep both in Source Control, you could:
1- Restore original state
2- Link DB to Source Control
3- Commit or...
Hi,
Any users that are using migrations in version 5, should update to version 5.2.3 or newer of SQL Source Control as this release addresses some bugs we have identified earlier.
Thank you, / comments
Hi,
Any users that are using migrations in version 5, should update to version 5.2.3 or newer of SQL Source Control as this release addresses some bugs we have identified earlier.
Thank you,
Hi,
We have opened a technical support ticket to deal with this issue.
I will email you directly shortly.
Thank you, / comments
Hi,
We have opened a technical support ticket to deal with this issue.
I will email you directly shortly.
Thank you,
Hi,
This is caused by a bug which is currently under investigation.
Thank you, / comments
Hi,
This is caused by a bug which is currently under investigation.
Thank you,
Hi,
We have opened a support ticket to troubleshoot your issue.
I will contact you using that channel shortly.
Thank you, / comments
Hi,
We have opened a support ticket to troubleshoot your issue.
I will contact you using that channel shortly.
Thank you,
Hi,
I have logged a support ticket and will get in touch with you through that channel to troubleshoot this issue.
Thank you, / comments
Hi,
I have logged a support ticket and will get in touch with you through that channel to troubleshoot this issue.
Thank you,
Regarding Option 1, the current version of SQL Source Control allows you to specify a mapped network drive as the location of the Working Folder, however in this case the user had mapped the drive with the account he had logged into Windows but was running SSMS under a different account.
Regarding Option 2, this message is usually a result of the commit not having an associated comment / comments
Regarding Option 1, the current version of SQL Source Control allows you to specify a mapped network drive as the location of the Working Folder, however in this case the user had mapped the drive ...
From the Database to your Version Control System, you would need to use SQL Source Control which only allows interactive commits using SSMS.
Thank you, / comments
From the Database to your Version Control System, you would need to use SQL Source Control which only allows interactive commits using SSMS.
Thank you,
Hi,
SQL Source Control only allows interactive commits as it's meant to be used on development databases.
We do however have a DLM Automation solution that allows automatic deployment from the scripts folder managed by SQL Source Control.
For further information please read/see: https://www.red-gate.com/products/dlm/dlm-automation/ https://www.youtube.com/watch?v=9lhBi2mkXrs
Thank you, / comments
Hi,
SQL Source Control only allows interactive commits as it's meant to be used on development databases.
We do however have a DLM Automation solution that allows automatic deployment from the scri...
Hi,
As detailed in the support ticket open this appears to be caused by a bug which we are currently investigating.
Thank you, / comments
Hi,
As detailed in the support ticket open this appears to be caused by a bug which we are currently investigating.
Thank you,