Comments
Sort by recent activity
Hi
Thanks for your question. Can I ask why you perform a 'switch'? Is it in connection with branching your database?
If so, we are currently considering ways for SQL Source Control to better support workflows where users want to branch regularly.
It would really help if you could you explain the workflow you go through when you 'switch', and then we can endeavour to take this into account when we design the new feature.
Best regards
Chris / comments
Hi
Thanks for your question. Can I ask why you perform a 'switch'? Is it in connection with branching your database?
If so, we are currently considering ways for SQL Source Control to better suppor...
Hi
You should be able to rollback static data using Red Gate's SQL Data Compare - if you have a license for this product. You will need to populate a scripts folder with the the schema and data changes you want to rollback to and then deploy that back to your development database. You could then commit the changes in SQL Source Control to effectively rollback the data.
SQL Data Compare v10.0 will be realeased in the next few weeks that will enable a new button on the SQL Source Control v3.0's History Dialog allowing you to rollback static data to a selected version.
Best regards
Chris / comments
Hi
You should be able to rollback static data using Red Gate's SQL Data Compare - if you have a license for this product. You will need to populate a scripts folder with the the schema and data ch...
Hi
You are able to reduce the frequency of SQL Source Control's database polling by setting an option in a confirguration file. For information see - http://www.red-gate.com/MessageBoard/vi ... hp?t=12837.
Best regards,
Chris / comments
Hi
You are able to reduce the frequency of SQL Source Control's database polling by setting an option in a confirguration file. For information see - http://www.red-gate.com/MessageBoard/vi ... hp?...
If you unlink and relink the object history will not be lost. This is all stored in your version control repository.
By unlinking and relinking to the same repository location you are just making a new local working base for SQL Source Control to interact with.
Best regards,
Chris / comments
If you unlink and relink the object history will not be lost. This is all stored in your version control repository.
By unlinking and relinking to the same repository location you are just making a...
Hi
Deleting the SQL Source Control v2 directory tree without first unlinking the database from SQL Source Control via the user interface would cause the behaviour you describe. Although, it is worth stating that SQL Source Control v3 will work fine with databases with a working base under the v2 folder.
However, if you'd prefer the working base to be under the "SQL Source Control 3" please unlink the database first, delete the unwanted working base folder and link the database again.
Best regards,
Chris / comments
Hi
Deleting the SQL Source Control v2 directory tree without first unlinking the database from SQL Source Control via the user interface would cause the behaviour you describe. Although, it is wort...
Hi
Can you please confirm what you mean by 'associated objects'?
In SQL Source Control version 3 we added Migration Scripts, which must be committed with associated objects. We also enforce changes to be committed together it they are Data and Schema changes related to the same object.
Would you be able to post some brief steps we can take to reproduce the issue?
Many thanks,
Chris / comments
Hi
Can you please confirm what you mean by 'associated objects'?
In SQL Source Control version 3 we added Migration Scripts, which must be committed with associated objects. We also enforce changes...
Hi
In the latest version of SQL Source Control there is no option to configure the comparisons performed by the product (unlike SQL Compare - as you mentioned).
However, we are currently working on adding a comparison options configuration file to SQL Source Control that will allow you to detect synonym changes (and change many of the other options available in SQL Compare).
We are hoping to release this in the next few weeks via our 'Check For Updates' mechanism. I will add a post to this thread when that build is available.
Best regards,
Chris / comments
Hi
In the latest version of SQL Source Control there is no option to configure the comparisons performed by the product (unlike SQL Compare - as you mentioned).
However, we are currently working on...
Hi
SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options (such as detecting synonyms) to be configured.
To get this version, please run Check For Updates from the Help menu in SQL Source Control. This is a free upgrade for existing licensed v3 users and for users with a Support & Upgrades contract.
Comparison options can now be set via a configuration file in your database repository's Working Base folder. The following Knowledge Base support article describes how to configure this option: KB201202000521 - Setting SQL Compare options within SQL Source Control
Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.
If you'd like to see an options dialog exposing these settings in SQL Source Control, please vote on the associated Idea on our UserVoice site. It'd be great if you could also leave a comment indicating which specific options you'd like to see in the dialog.
Best regards,
Chris / comments
Hi
SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options (such as detecting synonyms) to be configured.
To get this version, please run Check For Updates from the Help menu i...
Hi
SQL Source Control v3.0.5.7 includes a mechanism to allow 'Ignore FillFactor' to be configured.
To get this version, please run Check For Updates from the Help menu in SQL Source Control. This is a free upgrade for existing licensed v3 users and for users with a Support & Upgrades contract.
Comparison options can now be set via a configuration file in your database repository's Working Base folder. The following Knowledge Base support article describes how to configure this option: KB201202000521 - Setting SQL Compare options within SQL Source Control
Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often (which is likely to include fillfactor), but we believe this configuration file procedure should help users in the interim.
If you'd like to see an options dialog exposing these settings in SQL Source Control, please vote on the associated Idea on our UserVoice site. It'd be great if you could also leave a comment indicating which specific options you'd like to see in the dialog.
Best regards,
Chris / comments
Hi
SQL Source Control v3.0.5.7 includes a mechanism to allow 'Ignore FillFactor' to be configured.
To get this version, please run Check For Updates from the Help menu in SQL Source Control. This i...
Hi
Just to explain why this behaviour has changed - we had a number of requests to stop ignoring FILLFACTOR and INDEXPADDING by default in the comparisons that SQL Source Control performs. Ignoring these changes is the default option for SQL Compare, but we thought it was a change that SQL Source Control users would generally want to see.
However, what we really want to do is allow the user to configure this setting (as they can in SQL Compare)....
Therefore, we are currently working on adding a comparison options configuration file to SQL Source Control that will allow the user to set FILLFACTOR to be ignored if they so wish.
We are hoping to release this in the next few weeks via our 'Check For Updates' mechanism. I will add a post to this thread when that build is available.
Best regards,
Chris / comments
Hi
Just to explain why this behaviour has changed - we had a number of requests to stop ignoring FILLFACTOR and INDEXPADDING by default in the comparisons that SQL Source Control performs. Ignoring...