the ability to move column order
Example I would like the Owner Column next to the Object Name

We have gone though SQL source control and it workd perfectly with our Mercurial repository for schema changes. We also want some data changes to be source controlled like in some master tables , we have added some values. We want that these values should be added in the target database with the schema changes when the target db update itself by taking latest, so this type of feature i available in RedGate or we have to do some manual work for data changes. Kindly guide. Thanks

1) Source Control - Get latest: first schema's then udf's and xsd schema THEN the rest

If you have only the SQL Source control product, you can use it to upgrade your production SQL server database. But if you switch to Azure SQL, you lose this capability. I think the option to generate upgrade scripts that are Azure compatible would be great!

When I click on the popup window telling me that is is done getting latest for my database in the background, when I click on the (click here to go to the database) link, it resizes my SSMS window (almost looks like it does the restore down button between the x and minimize button in the upper right.

Maybe it is a bug. But code like

DROP SIGNATURE FROM dbo.mySP
BY CERTIFICATE [myCertficate];

is not recognized as a change. Please consider to support this

RCS keyword expansion expansion in Perforce is detected as a change when comparing DB and Source Control code. This is unhelpful. SQL Source Control should ignore changes in RCS tags content when the file type is set to KText

I accidently did an sp_rename 'DF_Visits_Some3234234', '[DF_Visits_SomeNumber]', 'Object' and committed it to SVN. Now, when I change it back, the Source Control does not detect this as a change to commit back. How do I get around this, or it's a bug.

I would like to be able to allow people to get a copy of the latest set of development functions, etc. kept in a repository. I don't want everyone to be able to write new/modify existing functions. Currently when they try to do a get latest, it errors out saying they need read, check in, check out, and lock permissions. To get around this I've given everyone full permissions in TFS. I don't understand why that would be necessary for a get latest.

Include StarTeam as a source control option

The pattern for migration script names should be a configuration. I would like my migration scripts to identify the version of the database instead of the revisions. Thus I would like to define the name of the migration script.

I would like to see more meta data columns on the migration script window. Name and Date create come to mind. Also tagging for specific environments (QA, Prep, etc)

SQL has the feture to view object dependencies. but, it dont have it for SQL logins. So, it will be good to have this feature in this s/w

If I cancel a commit, on the dependencies dialogue window, it seems to clear the original comments.

This usually happens if I forget to include an object for commit, and the popup dialogue reminds me. I know it offers to include dependencies I have missed, but this often I'll have meant to include other objects in the submit. If I click cancel to go back and add them, the comments have been cleared

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.

I had three different connection in SSMS. One for each user: Sql admin, webadmin, webapplication user. I think I by mistake made a commit from the connection for the webapplication user which have very few rights. All the users right got screwed up after that.

Bug: when creating a migration script for a table change that requires dropping Foreign Keys on other tables to this table, the generated migration script does not include the extended properties for the Foreign Keys on the other tables when rebuilding the Foreign Keys.