Comments
Sort by recent activity
Conclusion:
The difference was caused by an otherwise identical user being associated with a login in one database and not being associated with a login on the other.
These users appeared as equal in SQL Compare because the option Ignore User Properties is enabled by default in SQL Compare projects.
User was able to resolve the issue by using the Filter feature to exclude user objects. / comments
Conclusion:
The difference was caused by an otherwise identical user being associated with a login in one database and not being associated with a login on the other.
These users appeared as equal ...
Hi MckMurray,
Thanks for your post.
I have logged an incident on our support system and will follow up on this from there.
Thank you, / comments
Hi MckMurray,
Thanks for your post.
I have logged an incident on our support system and will follow up on this from there.
Thank you,
Hi Mark,
You are right the instance name change is the cause as that's how SQL Source Control tracks linked databases.
You won't have that issue if you use SQL Server Express.
Thank you, / comments
Hi Mark,
You are right the instance name change is the cause as that's how SQL Source Control tracks linked databases.
You won't have that issue if you use SQL Server Express.
Thank you,
Hi Mark,
Thanks for your post.
Information about linked databases is stored in "C:Users(username)AppdataLocalRed GateSQL Source Control 4LinkedDatabases.xml".
We've also opened an incident in our support system, so that we can determine what's causing the databases to unling when SSMS crashes.
Thank you, / comments
Hi Mark,
Thanks for your post.
Information about linked databases is stored in "C:Users(username)AppdataLocalRed GateSQL Source Control 4LinkedDatabases.xml".
We've also opened an incident in our s...
Hi Jeff,
We are currently working on a new migration model and enhanced Git support will be one of the main features. Shared databases should continue to be supported.
Thank you, / comments
Hi Jeff,
We are currently working on a new migration model and enhanced Git support will be one of the main features. Shared databases should continue to be supported.
Thank you,
Hi Jeff,
Thanks for your post.
Regarding your query, the recommended way in SQL Source Control to avoid loss of data when renaming a table is to use a migration script.
Please read the following for more detailed information: http://documentation.red-gate.com/displ ... on+scripts https://documentation.red-gate.com/disp ... +data+loss
I hope this helps, / comments
Hi Jeff,
Thanks for your post.
Regarding your query, the recommended way in SQL Source Control to avoid loss of data when renaming a table is to use a migration script.
Please read the following fo...
I am pleased to announce that as of version 4.1.13 (available on the Frequent Updates channel), SQL Source Control now supports TFS 2015 without Team Explorer installed.
Please read the linked webpage for more detailed information: https://documentation.red-gate.com/disp ... patibility
Thank you, / comments
I am pleased to announce that as of version 4.1.13 (available on the Frequent Updates channel), SQL Source Control now supports TFS 2015 without Team Explorer installed.
Please read the linked webp...
Hi,
Currently we still don't have an ETA on supporting Team Explorer 2015, I have created a support incident to see if you can help you with any issues you might be having using the earlier Explorer versions.
Please check http://documentation.red-gate.com/displ ... ease+notes to find out about new features in SQL Source Control.
Thank you, / comments
Hi,
Currently we still don't have an ETA on supporting Team Explorer 2015, I have created a support incident to see if you can help you with any issues you might be having using the earlier Explore...
Hi,
I am afraid there's still no hard ETA.
However this is likely to be implemented in the next 2-3 months.
Thank you, / comments
Hi,
I am afraid there's still no hard ETA.
However this is likely to be implemented in the next 2-3 months.
Thank you,
Hi GBoulton,
Thanks for your post.
Regarding the email address, the application only checks if there's a @ on the inserted string so you should be able to insert a no-reply@company.com.
I will follow up this post with an email from our support system and will ask you for more details on this error you are experiencing in order to try to understand what might be causing it.
Regarding the possibility to individualize notifications in the from field that seems a very good idea.
You may want to post it on the DLM Uservoice forum:
you and other users will be able to vote and comment on this idea. The DLM Product Management team takes the input provided on this forum as an important source when deciding what new features to add to DLM Dashboard: https://redgate.uservoice.com/forums/25 ... -dashboard
Thank you, / comments
Hi GBoulton,
Thanks for your post.
Regarding the email address, the application only checks if there's a @ on the inserted string so you should be able to insert a no-reply@company.com.
I will foll...