We use Mercurial for SCM and we can't use the 'History' option to rev our databases to a particular change as a result!

On the "Commit Changes" and "Get Lastest" tab, you should include the last date the object has been modified. So you will be able to sort/filter the objects recently modified.

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

I understand a hook can be added to SVN so if a commit is made without a comment it will throw an error and fail - From an interface point of view it would be nice the commit couldn't even be made (i.e. the button was disabled if a "require comments" option was set).

I often have to put together a changelist that essentially lists the affected objects (tables, SPs, etc.) for documentation purposes. In Tortoise, I can highlight one or more revisions then in a separate page, shift or control select several or all items and hit Control-C to copy that as text. Then I can paste it and get a nice long list of table names, SP names etc like this:

SomeTable
AnotherTabl
usp_myStoredProc
usp_SomeoneElsesSP

It's something I use for documentation and it just would make life so much easier. Not sure if it's a big deal to make that happen.

Displaying the History is awesome, but it would be nice to be able to modify the comments right there in the history window.

Turning off polling is not a straightforward task. And after I've used Source Control I have to exit SSMS and restart it in order to not have it generate a ridiculous about of traffic to my SQL Server 2012 SP1 instance. This has to be fixed or I'll find another tool.

Hi;
I need to review get latest list before accepting changes from the source control to the my local DB. While accepting these changes; I want to see who did this changes but I can see this only “show history” window.
Can we add this information into the get latest feature?

Thanks.

Kind Regards
Ali Bulut
DBA/Operations

I word like to hav the posibility to revert changes using a rightclick i history.
Both all (opper pane) the changes in a commit, and the changes to a specific object (middle pane).

We frequently execute DB scripts on dev machines and servers, and when default constraints are created in SQL they are given a randomized name. Since we have SQL Source Control installed in the same environments, we always get conflicts about the constraints being named differently in the source control vs. the current machine. The ability to turn of conflict (or even change) notification about some things like constraint names is needed to avoid having to deal with each case individually.

History window should indicate the fact that some of the changes are covered by the migration scripts and provide the ability to view these scripts

While viewing the history log you can't go to the main SSMS window. This is an issue if you want to look at source code history side by side with another window.

We have a 3rd party developer who sometimes tweaks things on our databases, i have to report and document these changes to management, currently, i have to either rely on screenshots, or copy and paste the before & after code and apply my own colouring etc. Something similar to VSS's change report would be ideal: example: http://www.heavencore.co.uk/filehub/Documents/ssreport.txt

Ít would be nice, if you dont have to be in sysadmin-role to see wich user has made changes. thx.

It would be nice to do a quick search across all migration scripts for certain keywords. I.E. I'd like to look for all migration where I granted permissions. Or where I inserted rows into a specific table.

Suggest that the SSCv3 installer NUKE all prior version Log folders e.g., SSCv2 and SSCv1, please...(or at least offer us the choice to have them nuked...) Had Stuart not posted (at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2526239-log-files), I'd have those two folders around for ever...

Show last history entry (version, author, etc.) per object in the list.
Create an alternative object explorer style page to do this.

Include an objects history in SQL Doc.

When comparing differences a double-click on the object could open a external diff viewer (if configured)