40 results found
-
require a commit message for git
Git requires a commit message by default however SQL Source Control circumvents this setting and commits without a message. There are a few other submissions attempting to get this fixed which have been declined. Seems you are missing the point.
In the case "Empty commit message for git is invalid" the very article you've linked points out that it takes special command line flag to commit without a message. SQL source control commits without a message and provides no mechanism to prevent this. There is no configuration for git that will do this because the default git behavior is already…
48 votes -
With Many databases source controlled. It would be great if there was a function to view changes and updates across all databases
With Many databases source controlled. It would be great if there was a function to view changes and updates across all databases. At the moment databases have to be updated one by one. very time consuming
36 votes -
Support for SCCI standard
Numerous source control products support the SCCI interface standard. We use 3 products between numerous clients. TFS, VSS, and Seapine SCM. Another possibility is PureSCM.
34 votes -
Link databses using solution or project file
We have a lot of databases. It's very time consuming to link all databases one at a time for every developer. It should be possible to make use of a solution file to link a solution with all the databases, rather then mapping one by one.
25 votes -
Option to disable the SQL sp_refreshview command in the update script.
An option that prevents the addition of the EXEC sp_refreshview in the update script.
When updating queries that rely on linked servers and the linked server doesn't support distributed transactions the update fails and is rolled back.
Now we constantly have to manually alter the script by manually removing the EXEC sp_refreshview commands. This our server admins will not enable the DTC coordinator on the SQL servers
24 votes -
Integrate with IBM Rational Team Concert
Any plans to integrate with IBM Rational Team Concert?
23 votes -
accurev
I'm missing native support for AccuRev (http://www.accurev.com/) in the SQL Source Control product.
18 votes -
A way to select the database from the tab itself.
I develop and have to switch between multiple databases and the source control tab keeps following the database I am on. When I want to commit changes I have to stay put otherwise I keep losing the progress looking for changes. It would be nice to have the option of which database we are looking at from the tab itself, instead of from the SQL Management Studio one
16 votes -
Add "Select Object in Object Explorer" in Commit changes tab
Add option like SQL Search application for quick acces to object
16 votes -
Automated Deployment based on TFS work item status
I would like a way for SQL Source control to leverage TFS work item status and facilitate automated deployment similar to lab management.
13 votes -
clearcase
Would be nice if SQL Source Control supported clearcase, or if an example of the config file usage were created.
13 votes -
12 votesJames Billings 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
-
Export / import Link Database configuration setting for shared mode
It is very hard to do manual database link to repository/SVN if dealing with large number of databases (200 plus within one team) across large number of source control group. Every team member has to spend time and carefully map repository folder.
One user perform manual link to repository and his/her/ setting validated by QA Team before distributing link config file (xml) to the user group.
The basic requirement is user should be connected with the DB server and pass the repository path and credential. you may design few screen to navigate and collect user input based on provider input…
11 votes -
I would like to see a command line interface added to the SQL Source Control. Having this to be able to automate saving change into TFS
Have asked for this from support several years ago when the Source Control first was offered. Surprised still no command line interface. The ability to automate saving db changes automatically into TFS or GIT would be widely accepted by the DBA community. I would purchase it tomorrow if was made available.
9 votes -
Add commands
Being able to add our own commands that appear when you right click an object in SSMS.
9 votes -
Locking/unlocking functionality
Get rid of the option for anybody to unlock an object, but instead allow to unlock only by the person that locked the object or by a group in group role in the database where only few people have access.
8 votes -
Support for Dynamsoft SCM
We're using Dynamsoft SCM for source control. Currently, we're using sql prompt/sql changeset to script to a folder and then push that into SCM. It supports the SCC interface, but since you guys said that was too unreliable to use we're pretty much stuck.
7 votes -
Ad fields (commit name) into Change_Log Database
Add Commit name in ChangeLog DB
To manage release in DB Commit name can be add where ChangeLog DB is active.
The goal is to use This DB to log the name of the last commit for an object. it can be use for a lot of cases.6 votes -
database properties
Redgate still does not Support Database properties??
They shuold support properties like (Transaction Isolation level (Read Committed, Snapshot)Ansi Null, Quoted Identifier). These are Crucial. I cannot believe these are not in source control yet. The product has been out since 2006.
6 votes -
I would like to be able to print to file (pdf, excel) the table of changes shown in source control.
Print the changes displayed by source control to pdf, excel, csv.
6 votes
- Don't see your idea?