178 results found
-
Clean up temporary TFS workspaces when using sql compare
Apparently SSC creates temporary workspaces when being called from SQL Compare (when using a source controlled version of the database as the source of the comparison), but it doesn't seem to clean up after itself completely. When I go to manage my workspaces in TFS, it is currently showing that I have over 50 temporary workspaces that were created by SSC. I can't swear to it, but I think this may have caused issues with our builds, as I have observed at one point that I inadvertently checked code files out to one of these temporary workspaces instead of my…
3 votesSQL Source Control 3.0 is now available which includes a fix for this issue.
TFS workspaces are created when linking to a database in SQL Source Control – from v3.0 these are deleted when the database is unlinked.
To download v3, please visit:
http://www.red-gate.com/products/sql-development/sql-source-control/ -
The browse button for the Source Control Folder on Link to Source Control pane
The browse button makes using the product so much easier. Thanks for adding it.
1 voteGlad you like it. This is available in v2.2+ for SVN, TFS, and Vault. :-)
-
Unable to change migration settings on the 'Setup' tab v3.0.0.50
After connecting Source control to the database, I am unable to change the Migration settings on the 'Setup' tab.
0 votesMigrations in SQL Source Control 5 no longer requires a separate repository, so you should now be able to use it with your setup.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
If you’ve stuck with us since 2011, many thanks. If not, maybe now is a good time to give the product another look? :-)
-
Regular Expressions in Filter
When setting up filter rules, it would be useful if we could use some regular expressions on the criteria. We have several objects that we would like to exclude from source control when they end with a string of 6 numbers. The numbers are different for each object, so if we could use some simple regular expressions, we could filter out objects that end with [0-9][0-9][0-9][0-9][0-9][0-9].
5 votesAs of SQL Source Control 3.8.13, filter rules now support the standard T-SQL LIKE syntax for wildcard characters (‘%’, ‘_’, ‘[abc]’, and ‘[^abc]’ – see MSDN for details).
To include wildcard characters explicitly in a filter, they can be escaped with square brackets.
‘Equals’ and ‘Does not equal’ operators will not treat those characters as special wildcard characters.
-
Fix bug with Change Tracking
There is a bug with change tracking on both SQL Source Control and Schema Compare. When a script is generated to alter a table that has change tracking already enabled, the ENABLE CHANGE_TRACKING script is added to the script causing the whole script to fail because change tracking is already enabled. This bug has been there for a long time. This bug is making both products difficult to use. It has been reported multiple times but has not been fixed yet.
25 votesSQL Source Control 3.0 is now available which includes a fix to this issue.
For more information about the release, please see:
http://www.red-gate.com/MessageBoard/viewtopic.php?t=14421 -
Centralized uninstaller
I had to uninstall RedGate SQL Toolbelt today, and this involved uninstalling 13 separate products individually. It would be nice if the easy installer could uninstall just as easily.
(So you aren't disappointed that I uninstalled: I was switching over to the MySQL tools.)
54 votesWe now have a centralized uninstaller (this will not work when uninstalling products before they were updated with the new uninstaller)
-
show history for dropped objects
I dropped a sp and I would like to know in which version I dropped it (I'm entering our version number in the comments)
2 votesHistory is shown for dropped objects. Right click on the database or the object’s folder (e.g., Tables) and select show history. You will see dropped objects in the list.
-
Support SQL Compare Project Configuration Options
When evaluating schema for changes compared to source controlled versions is would be nice to be able to use the same options available in SQL Compare project options.
For instance changing a comment on a line already containing a comment isn't detected as a change, additionally format (whitespace) changes are not detected as well.
While this specific scenario is important to my development process not everyone will need the same scenario supported, but the compare options available in SQL Compare are a great place start allowing users control how changes are detected.
40 votesSQL Source Control v3.0.5.7 includes a mechanism to allow comparison options to be configured. To get this version, please run Check For Updates from the Help menu in SQL Source Control.
Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to configure this option: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521
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 following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.
-
On a shared model, the Changed By column says unknown for some uncomitted changes on the Commit List
When I try to commit changes it says unknown user. I believe it is very important to be able to track who's making what changes.
112 votesIn v3.1, we store user information when an object changes so you don’t see “unknown” on the commit list for changes on a shared model. Details are at https://documentation.red-gate.com/display/SOC32/Logging+changes+to+shared+databases
-
Doesn't support views with schemabinding on
We have views with schemabinding set to true in SQL2008, SQL Source Control does not recognize that there is a dependency and throws and error.
3 votesHaving tested this out, the product does handle the schemabinding option on views. If a table needs to be rebuilt, it will alter the view to remove the schemabinding, update the table, then alter the view again to put the setting back.
The specific problem here was unable to be determined after following up with Nick and may have just been a one-off.
-
Ignore Permission Changes in Source Control
We are only interested in source controling the object definitions. We have a lot of volatile permission changes which we don't want to record, and its actually a hug obstacle constantly having to go in and check off 300 objects to commit just because someone changed a users permissions on them.
62 votesSQL Source Control v3.0.5.7 has been released and allows you to configure comparison options – inlcuding ‘Ignore Permissions’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.
Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to do this: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521
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 following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.
-
Redgate source control does not seem to recognize column Index's fill factor..
Redgate source control does not seem to recognize column Index's fill factor..
26 votesSQL Source Control 3.0 is now available and includes a fix for this issue. Fill Factor should now be recognised by default.
For more information about v3, please visit:
http://www.red-gate.com/products/sql-development/sql-source-control/Further Update: SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options to be configured. To get this version, please run Check For Updates from the Help menu in SQL Source Control.
Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to configure this option: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521
-
Choose when to calculate static data changes
Our static data tables can have a few thousand rows each. It's costly to have the rows compared every time the SQL Source Control tab is opened to push/pull schema changes (which are much faster to compute). Can the schema and data aspects of this tool be separated to prevent excessive comparisons on data that by nature changes very infrequently.
14 votesThe option to disable data change detection is now available from the Setup tab in the Frequent Updates build, and will be available in the next main version of the product.
If you want to get the Frequent Updates builds, more details can be found at http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates.
-
Add Last User Modified
On the Commit Changes and Get Lastest tab, you should include the last user that modified the object. Far too many times I have to ask all the developers to identify the objects that they have changed yet not committed. It would be nice to be able to see that.
1 voteIn v2, when you are working on a shared model, we show who has changed the object in the database on the Commit tab. We also only check your own changes by default.
If you would also like to see the last person who committed when you Get Latest, please vote/comment on http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/1375333-show-who-committed-the-changes-in-the-get-latest-l.
-
Link to a database already in source control
the option seems to have been removed in Source Control 2, we really found this a helpfull option so we wonder why is was removed.
1 voteThere’s only 1 link, but it can do either. If you link to an empty folder, then that’s like a “new” link. If you link to a folder that contains a RedGate.ssc file, then that will link to the existing repository location. :-)
-
3 votes
There was a bug in the first EA, which caused problems when trying to do the initial commit for large number of objects. It’s now fixed, please get the latest version.
-
Committing large number of changes on CVS fails
When committing large numbers of changes under CVS, the commit fails with error message 'command line too long'.
1 voteFixed in EA version 2.0.3.13. You can get the latest EA version from https://www.surveymk.com/s/SqlSourceControl_EapSignup
-
Make RedGateDatabaseInfo.xml easier to merge
When we look at the RedGateDatabaseInfo.xml file, it appears as one long line of text. Merging this is nigh on impossible because the one line conflicts. It would be nice if it was written in a pretty xml format to help with merging
3 votesForm Source Control version 2.1, RedGateDatabaseInfo.xml should now be in a more structured format.
Please comment on this suggestion if this new structure does not meet your requirements.
Please visit our product page for more information on the latest version of SQL Source Control:
http://www.red-gate.com/products/sql-development/sql-source-control/ -
Treat column ordering as a change
I know it doesn't really matter, but I like my columns to be in a consistent order. I would like any table DDL to cause the table to be regenerated if necessary in order to ensure that column ordering is maintained.
21 votesGood news …This is now available on SQL Source Control v2.1 :)
-
Integrate with Fortress Item Tracking
When checking in changes allow the user to link the changes to a Ticket ID in Fortress Item Tracking, adding a comment to that ticket and adding the ticket ID/details to the checkin comment. Also optionally allow the user to complete the ticket when checking the changes in.
1 voteUsing the latest Vault EA build (1.1.3.49) it’s possible to connect a commit to a ticket id. An example comment you could use to mark bug id 4 as completed:
Fixing that old bug #4 #completed
You can use any status string you have in use instead of completed.
- Don't see your idea?