SQL Source Control
Thank you for evaluating SQL Source Control. Your feedback will impact what we do next!
-
Support Symmetric keys
BUG:Inital commit, Symmetric key is not added to TFS. atleast show the user that these list of items he has to add them himself
1 voteUnfortunately, we currently can’t source control asymmetric keys, symmetric keys, or certificates.
-
Auto checkout from TFS on modify of sql object. and show the object as checked out in SQL Mgt Studio
Auto checkout from TFS on modify of sql object, and show the object as checked out in SQL Mgt Studio for other users in case of shared configuration.
72 votesSimilar to TFS checkout suggestion, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/802123-tfs-exclusive-checkout-svn-lock. I guess the difference here is that it is an option to do the checkout automatically.
-
Make it faster!!!! Improve Performance!!!
Oog, each commit is like five minutes. Neither standard commits of source code (same SVN server) nor redgate SQL Compare actions (same local database server) take that long!
Keywords: Performance, Speed, Fast
263 votesWe have made some improvements to the time taken to populate the commit list in SQL Source Control v3.0 (released on 15th Dec 2011).
However, we have started further work on performance and hope to be able to make significant improvements in v3.1.
Contact support@red-gate.com if you can share your database with us for testing purposes.
If you experiencing problems with server load, please see http://www.red-gate.com/messageboard/viewtopic.php?t=12837. Contact support@red-gate.com if you have any questions about this.
-
Work with a Visual Studio Database Project
Can this work if I already have a VS Database project setup? Meaning can this work and interact with a VS Database project so that I can continue working on the actual db in SSMS, but the files get saved to the VS Db Project?
144 votesThis is now available in the full release of SQL Source Control, http://www.red-gate.com/products/sql-development/sql-source-control, but it is still a beta feature.
SQL Source Control can link databases to the most recent version of Microsoft database projects (those folders containing a .sqlproj file).
It’s important to stress that this is a beta-quality feature, and as such it is only intended for experimental use. In particular, we are aware of some limitations regarding database-level extended properties, permissions and CLR assemblies. If you encounter these limitations or any other problems with this new SSDT compatibility, please let us know by using the Feedback link in SQL Source Control or contacting support@red-gate.com.
-
support for custom templates
Ability to use custom templates, i.e. for table creation, to be able to add EXIST / DROP statements and permissions
9 votes -
default password
create an option to change the default password it uses when creating users
3 votes -
When unselecting a specfic item allow for unselect of dependent items
If I unselected an assembly (since it is 32bit and I am x64) allow me a way to unselect all dependent objects easily. If I don't select an item I have a prompt to select dependecies but not the reverse.
1 vote -
Command line tool (or API) for SQL Source Control Integration
We have an automated system for building our developer environments. It would be nice to have a command line tool that we can use as part of the machine build script to pull down the latest version of the database, build the initial database and link that database back to the TFS source. Our platform consists of quite a large number of databases so linking to them all manually via the UI is a bit tedious.
93 votes -
choose subfolders in subversion
When adding a database to source control, all kinds of subfolders as created(data,assemblies,...) but these folder are not finegrained enough. for instance we do it by schema first then we use the same kind of subfolders.
So if we have a Import and Base schema, then in subversion we have the procedure/functions folder under Import and under Base.It would be nice to be able to choose the folders themselves and also where to put a function and so on.. this gives more flexibility.
3 votes -
Get Latest doesn't appear to work
Backup a database which is under revision control (with SQL Source Control), modify an SP and commit it. Then restore the DB (rolls back the SP). Source Control see the changed SP and allows me to commit it, but Get Latest doesn't.
3 votes -
Table Lock Escalation property change not detected
Changing the Lock Escalation property of a table in SQL 2008 SSMS is not detected as a change by SQL Source Control.
11 votes -
Support Serena PVCS archive
We have used PVCS for 15 years for all our development source control. Is it possible to connect RedGate source control to a PVCS archive?
1 vote -
bugid
Project management issue tracking software (Gemini, JIRA etc) use BugID to link checkins against issues. This allows for a managers to oversee progress on issues and other things (eg: risk of change, code review etc). The SVN BugID (a checkin property) is how a development code checkin is linked to an issue. Add this, and I can integrate our solutions easier at a CMMI level 3-5
33 votesFor now, enter your BugID into the comment field when you commit changes.
Please continue to vote/comment here if you would like to see a seperate Bug ID box like TSVN has. See James’ comment for more details.
-
Auto complete changed object names in commit message
It would be very cool if this tool would auto complete changed objects in the commit message like TortoiseSVN.
6 votes -
workspace per database, instead of per user account
At current we have SQL source control running in a remote environment. However, a DB - SVN link is stored for each user account, and is not transparent to the other developers.
Worse yet, with each developer having their own workcopy in their local profile, the same data will be duplicated several times. Also: conflicts will arise since each workspace updates on its own, while the DB might already be updated from another workspace.
Therefor: Suggest to keep 1 workspace per DB, to prevent issues of multiple workspaces or repositories linked to the same DB.
4 votes -
12 votes
AdminJames Billings
(Admin, Red Gate)
responded
If MKS offers a command-line, you may be able to configure it with config files – see http://www.red-gate.com/supportcenter/Content?p=SQL%20Source%20Control&c=SQL_Source_Control/help/2.2/SSC_working_with_config_files.htm&toc=SQL_Source_Control/help/2.2/toc1432725.htm
-
Scroll beyond teh current page when seleting multiple items
I can select multiple items by click/draging over the items, however it will only allow me to select what is on the current screen.
1 voteDo you have a wheel on your mouse? Once you highlight the items in view, just roll your mouse wheel to keep going down the list.
Another way to do this is to click the first row, hold the shift key down, and scroll down to the last row and click again. This will allow you to highlight everything.
Also, there’s a checkbox in the column header of the Commit/Get list if you want to uncheck/check everything all at once.
I hope this helps.
Stephanie Herr
Project Manager SQL Source Control -
scary stuff when you minimal privileges
I recently connected to my database as a new user with minimal privileges (just data_reader). Later I went to SQL Source control to see changes (forgetting I was logged in as the restricted user) and the output was scary - every SP was marked as deleted and most tables were marked as edited (text replaced with 'encrypted').
I didn't have the courage to hit commit just to see what happened - it was too scary seeing my entire database marked for deletion!
3 votes -
Allow commits to occur with other code changes
For continuous integration purposes, I would like to commit schema changes with changes in my project (e.g. C#) so that any related changes to classes / unit tests are commited in the same revision.
26 votes -
Change btn txt on the 'Get Latest' tab.
Button says Get Latest. Incorrcet Subversion term. SVN Update or something similar will prevent the confusion.
5 votes
- Don't see your idea?