It seems that right now migrations only support SVN, TFS and Vault - none of which I'm willing to use anymore. Please consider prioritizing support for Git/Mercurial.

Please add Git support for migration scripts

Please can we have migrations functionality for Perforce SCM

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.

We are using Visual Source Safe and we really want to source control our databases. We are not upgrading or changing our source control system anytime soon. Visual Source Safe works fine for us. We do not want to install a seperate source control system just to use this tool.

TFS Preview is TFS on Azure and although I can use the current process to set up using my TFS Preview URL TFS Preview uses Windows Live Credentials to connect, if I put them in the user name/ password boxes the connection fails.

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.

Would be nice if SQL Source Control supported clearcase, or if an example of the config file usage were created.

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

Any plans to integrate with IBM Rational Team Concert?

Being able to add our own commands that appear when you right click an object in SSMS.

Team Foundation Server Proxy Server is excellent for saving time and bandwidth when connecting to TFS over a WAN link.

SQL Source Control doesn't seem to support this functionality at present

I would like a way for SQL Source control to leverage TFS work item status and facilitate automated deployment similar to lab management.

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.

The source control system keeps thinking a certain table wasn't committed, and marks it up as "changed" to be committed. Here's the table:

-- Columns

CREATE TABLE [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
(
[CicloEducativoId] [int] NOT NULL,
[EvaluacionId] [int] NOT NULL,
[Grupo] [int] NOT NULL,
[ProfesorId] [int] NOT NULL,
[CursoId] [int] NOT NULL
) ON [PRIMARY]
GO

It doesn't seem to detect this line, and decides it has to insert it again:

DISABLE TRIGGER [dbo].[tD_EvaluacionesCicloEducativosGruposAcademicos] ON [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
GO

At the time of this writing, it has inserted the very same section 4 times, one after the other, and wants to keep doing it.

Working in a Team development, I do not want changes not to be commited to TFS. If I forget on closing, then a pop up window should ask you if you want to commit your changes.

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?