47 results found
-
It would be great to see the changes before they are commited to the source control
This would be a comparision between the local version of the files (e.g. loaded from the database) with the latest release on the version control system.
1 vote -
Provide Security for the Delink Database option
Provide a mechanism, either internal to SQL Source Control or via Active Directory, to prevent the Delink Database option being selected by any user. This is to ensure that all changes are tracked via SQL Source Control.
3 votes -
Revert changes show in History
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).7 votes -
Better implementation of Workitem checkin/tracking
Would it be possible to add under the Commit-comment field a dropdown or list which shows the data of a TFS-"Team Query"?
We have implemented a "CheckIn"-Query which shows the developer his open Tasks/Bugs/... so that he can just select out of this list while checking in the pending changes.
Entering the IDs manually is annoying and most of the developers don't do it because they have to go to the TFS first, catch the ID go back to SQL Server Management Studio and write the text.
In VisualStudio this works fine - the developers just change the tab and…17 votes -
The undo feature automatically disables your database triggers. I don't want my database triggers disabled.
We use DB triggers to track schema changes. If we use the Undo feature, it disables the triggers and we no longer are able to record the history apart from our source control system. Source Control is great, but we need to know exactly who made changes and when.
2 votes -
Need ability to suppress conflicts about constraint name changes.
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.
9 votesSQL Source Control’s Get Latest should be used in a dedicated model to update your different dev machines. This would keep the constraint names consistent in your dev environment.
You can use SQL Compare to deploy changes to other environments. SQL Compare has an option to ignore constraint and index names so that these differences won’t appear.
-
Display date of changes
We are using this in an active DW environment. The date of the change would be a helpful SSMS column. We like to see what changed, even in non-checked in work.
1 vote -
object revisions
Perhaps this already exists, but I couldn't easily find it by searching. We are using SVN as a backend. When checking in files, the "revision" number seems to be incremental based upon a global revision number, and NOT the actual revision number of the object being checked in.
If I'm creating a brand-new procedure and I check it in, the revision number should be 1??? Not 152 or some other number.
This way, after many changes, of when I want to go back to a prior version, you can easily find it!
Can this please be added?
8 votes -
Clone db from server to other server
Clone db from server a tomserver b without genarating a bk file
Direct bk restor without generating file
This alow to save time and space1 vote -
Why do you have to be in sysadmin-role to see who checked in changes?
Ít would be nice, if you dont have to be in sysadmin-role to see wich user has made changes. thx.
5 votes -
show migration scripts in the history window
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
10 votesWe have been working on v2 of Migrations, which stores migrations scripts in a table valued function within the database. This table valued function appears in the history. An Early Access Release of SQL Source Control is now available and can be downloaded from http://documentation.red-gate.com/display/MV2.
NOTE: This is an Early Access Release and is not fully tested or functionally complete yet. It would be great if you could try it in a test environment and let us know about your experiences so we can fix any issues and try to make any updates you need before the full release.
Thank you!
Stephanie Herr :-)
SQL Source Control Product Manager -
This app to too chatty with the database! Turning polling off is not straightfoward to do like it should be and once you start Source Contro
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.
8 votes -
History window shouldn't prevent access to main window
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.
16 votes -
Spell Check on comments.
Spell check on the comment text box would be helpful. Once a comment is checked into mercurial it is hard to fix the misspelled comments.
3 votes -
Search migration scripts for keywords
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.
7 votes -
Add support for ADD SIGNATURE / DROP SIGNATURE
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
16 votes -
Cancel commit clears comments
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
2 votes -
Installer to offer option to remove older version log folders
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...
2 votes -
Add ability to generate a list of affected objects
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
uspmyStoredProc
uspSomeoneElsesSPIt'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…
10 votes -
Select multiple versions in History
In SVN log you can select multiple revisions and the changes list will display changes "files" across all of the revisions. Would like to see this feature in SQL Source Control history.
1 vote
- Don't see your idea?