47 results found
-
Allow 'History' option for command-line SCM
We use Mercurial for SCM and we can't use the 'History' option to rev our databases to a particular change as a result!
46 votes -
Add "Modified Date"
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.
46 votes -
Keeping history of locked and unlocked objects
Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.
It would require very few changes - additional history table,
[SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.
Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.
19 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 -
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 -
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 -
SourceControl occupies gigabtyes of old files
Today, my Windows C: device was 99% full. During the search of the biggest files (which were the Windows/assembly/ folder) I noticed gigabytes of SQL Source Control files! Back to Source Control Version 3.x and 4.x even though we already updated to 5.x. Source Control does not clean up old files.
Directories I found old Source Control files:
C:\Windows\Downloaded Installations\
C:\ProgrammData\Downloaded Installations\
C:\Users...\AppData\Local\Red Gate\Please provide a function do uninstall all those old files that occupy even gigabytes of disk space storage. Thank you!
16 votes -
15 votes
-
See incremental changes made before committing
When working with an object, there is a chance that another developer has made modifications as well since many developers work off of the same database.
When committing, it would be nice to be able to see a history of modifications. Each time an object is modified (F5) take a commitable snapshot of that object.
When a developer goes to commit, they could see the different times an object was modified and commit all at one time or commit the individual changes made over time. Doing a commit will roll-up all previous commits made.
Example:
Day 1: Dev A: Adds…13 votes -
Keep history when the linkpath has changed (Subversion)
When unlinking and linking the database again with a new link path, you loose the ability to view the history. In Subversion clients like TortoiseSVN there's a Checkbox which let you se the history. Would bee great if SQL Source Control cold support that feature too, instead of having to go via TortoiseSVN each time I want to se the history of a certain object.
12 votes -
Option to use modification date as the commit date
With SQL, when you modify an object, that object is now out there to be used or tweaked by other developers. Committing it is really just a statement of, I'm done working with this object and here's what I've done.
We have the problem of not committing objects as timely as we should. We make a modification and go our way until we realize a week later, we forgot to commit. So we commit, but the date time stamp of the commit is not helpful. That is just when the developer remembered.
I think it would be much, much more…
11 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 -
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 -
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.
-
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 -
Add 'Work Item Number' to the History screen for TFS users
Add a column in the results for TFS customers so that they can see what Work Item was associated with the changeset
8 votes -
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 -
Support from Red-Gate SQL Backup command line tools on linux for sql server
Title describes it
7 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 -
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
- Don't see your idea?