Activity overview
Latest activity by csmith
Hi David,
Thanks for your post. I believe the SQL Lighthouse Team responded to the support request you raised on this issue. For the benefit of visitors to the forum I just wanted to note what happened with this - we couldn't recreate the problem at this end and added more logging into the SQL Lighthouse trigger in order to dig into the issue. Unfortunately, the problem seemed go away once the new trigger was installed and procedure creation worked again. Is this still the case?
Please let us know if you hit this issue again and we'll try to get to the bottom of the problem with you.
Best regards,
Chris / comments
Hi David,
Thanks for your post. I believe the SQL Lighthouse Team responded to the support request you raised on this issue. For the benefit of visitors to the forum I just wanted to note what happ...
SQL Lighthouse Beta Released!
Hi all,
I’m pleased to announce the beta release of SQL Lighthouse!What does the SQL Lighthouse beta do?
We built SQL Lighthouse to allow DBAs and database developers to identify and respond to d...
Shared Model Improvements Release
HiUPDATE:
I'm pleased to announce the Full Release of SQL Source Control v3.1 that includes improvements to the audit information provided in the 'Shared Model' environment. To install it please in...
Hi
I'm afraid we have not been able to reproduce the problem you've described here. Having found the content below, we suspect it might be an issue with SSMS: http://social.msdn.microsoft.com/forums ... 5b7a98be0/ http://blog.ronhsu.com/2010/01/18/sql-s ... -password/ http://connect.microsoft.com/SQLServer/ ... properties
Best regards,
Chris / comments
Hi
I'm afraid we have not been able to reproduce the problem you've described here. Having found the content below, we suspect it might be an issue with SSMS:http://social.msdn.microsoft.com/forum...
Hi
Thanks for your post. I did realise that you were renaming a table but I was focussing on deploying & sharing these changes, in which case Migration Scripts are how we'd recommend you handle the issue.
In terms of underlying filename in the repository, which I think is your concern, we do not attempt to perform an SVN rename on a file because we have not identified the rename operation. This is because in order to determine what appears on SQL Source Control's commit tab the application performs a comparison between the state of the sql files in your repository and the live database you are developing against. Unfortunately, this comparison cannot automatically tell the difference between a user dropping a table & adding a new table, and a user renaming a table.
I understand your frustration that this is not an automatic process. We plan to enhance the comparison logic in the future to recognise a rename (perhaps by comparing Object IDs, or column similarities), but I cannot give you a date for when that work would be completed. In the meantime, you could add a migration script around the commit, including the appropriate sp_rename calls.
Committing a 'table drop' and a 'table add' to the repository becomes a problem when it is time to deploy changes from a repository into a test, staging or production environment using SQL Compare, or when another user of SQL Source Control performs a 'Get Latest' operation. This is because any data in the table will be lost when it is dropped and re-added. This is one of the reasons we added the Migration Scripts feature.
If you'd like any more help with the Migrations feature, please let me know or email support@red-gate.com.
Best regards,
Chris / comments
Hi
Thanks for your post. I did realise that you were renaming a table but I was focussing on deploying & sharing these changes, in which case Migration Scripts are how we'd recommend you handle the...
Hi
In version 3 of SQL Source Control we added the Migration Scripts feature to handle this and other scenarios that could cause data loss (see this post on our feedback site).
The feature allows users to add a custom upgrade script around a change (or changes) in order to override default comparison/deployment behaviour. For more information about Migrations, please visit: http://www.red-gate.com/supportcenter/Content/SQL_Source_Control/help/3.0/SSC_Working_With_Migrations.
Best regards,
Chris / comments
Hi
In version 3 of SQL Source Control we added the Migration Scripts feature to handle this and other scenarios that could cause data loss (see this post on our feedback site).
The feature allows u...
Hi Janos,
SQL Source Control and SQL Compare do not yet support the new object-types introduced in SQL Server 2012.
We plan to add support for the new objects incrementally, starting with Columnstore indexes and File table support. Customer demand will dictate what new objects we add support for next, so with that in mind you could add a suggestion to our user feedback site - UserVoice- asking for Sequence support.
So, just to confrim - SQL Source Control works with SQL Server 2012 SSMS and can connect to SQL Server 2012 databases - but can only understand SQL Server 2005/2008 compatible objects.
Best regards,
Chris / comments
Hi Janos,
SQL Source Control and SQL Compare do not yet support the new object-types introduced in SQL Server 2012.
We plan to add support for the new objects incrementally, starting with Columnsto...
Hi
We believe SQL Source Control should work on a French version of Windows (although the UI is not localized). I've asked a few questions below to help us diagnose the problem:
1. Did you only have one instance of SSMS open? Because SQL Source Control will only appear in the first instance of SSMS opened.
2. Which version of SQL Source Control and SQL Server SSMS are installed on the IT director's computer?
3. Can you confirm that there is an registry entry at the following location on the director's computer:
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\Downloads\SQL Source Control\3
Best regards,
Chris / comments
Hi
We believe SQL Source Control should work on a French version of Windows (although the UI is not localized). I've asked a few questions below to help us diagnose the problem:
1. Did you only ha...
Hi
We’ve recently added a configuration file option to allow users to turn off Data Comparisons in SQL Source Control. This is available in the latest version that you can get by going to the Check For Updates item on SQL Source Control's Help menu.
To turn data comparisons off you need to do the following:
1. Close SSMS.
2. Open the following file - C:\Users\[username]\AppData\Local\Red Gate\SQL Source Control 3\ RedGate_SQLSourceControl_Engine_EngineOptions.xml
3. Add the following IgnoreDataDirectory tag inside the EngineOpions tag:
<?xml version="1.0" encoding="utf-16" standalone="yes"?>
<!---->
<EngineOptions version="2" type="EngineOptions"> <IgnoreDataDirectory>true</IgnoreDataDirectory>
</EngineOptions>
4. Save file and restart SSMS.
Of course, you will have to change the 'IgnoreDataDirectory' value to be 'false' if you want to start comparing Data again.
Please let me know if this process works ok for you - and if you would like to see this option added to the user interface somewhere.
Best regards,
Chris / comments
Hi
We’ve recently added a configuration file option to allow users to turn off Data Comparisons in SQL Source Control. This is available in the latest version that you can get by going to the Ch...
Hi
I believe there was a logging bug in that version of the product that we have subsequently fixed. Can you please download the latest version via the Check For Updates option in the SQL Source Control Help menu?
If the problem still occurs, please contact support@red-gate.com and we will do what we can to resolve the issue.
Best regards,
Chris / comments
Hi
I believe there was a logging bug in that version of the product that we have subsequently fixed. Can you please download the latest version via the Check For Updates option in the SQL Source C...