588 results found
-
Adjust tab order on "Link to Source Control" Screen
The source control folder field currently tabs upward to the question mark next to "Type or paste the URL.....". It seems that it should tab to entry 1 under "development model"
1 vote -
Add "Save as..." option to history 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
5 votes -
CVS cannot handle $Log entries in
In CVS you can use the $Log keyword within, say, a stored proc definition and CVS will automatically insert the commit comments. Works very nicely, but the problem with SQLSourceControl is that the file is updated by CVS on commit when it inserts the new audit comment. However, SQLSourceControl thinks the file has changed and wants you to commit it again. Any chance of this being resolved, perhaps ignoring the $Log section when detecting if the file has changed?
1 vote -
Make TFS Source Control Folder case insensitive...
...when Linking a database, please!
3 votes -
Automatically Check for Changes and check those changes in periodically.
If I could have the product walk a bunch of databases on a server (like a dev server) at 4 PM every day and check in any changes either completely automatically or with a single click for all dbs that would be sweet.
Another use case for this is when I have to revoke a users rights to a bunch (20 or more) databases on a server with a script but then have to check in the change on each db one at a time.
6 votes -
showing table row count in the link static data screen could help avoid adding large tables
don't have to perform a count, just a quick look at sysindexes would be sufficient.
3 votes -
source control folder structure should reflect that in ssms. in particular for indexes
source control folder structure should reflect that in ssms. in particular for indexes
1 vote -
Import/Export settings
I had to recreate a user profile and AppData\RedGate folder copy did not retore linked databases cleanly. Would like a method to export settings for use with profile recreation, sharing with other team members, backing up configuration before making changes.
29 votes -
4 votes
-
tab button behaviour on Link
When I enter the server details to create link and then hit the tab key, the cursor focus should go to the field for the path. It seems to go everywhere else and not end up in the expected field for a further 5-6 tab key taps.
1 vote -
Unable to load a project file after installation
After installation, I was no longer able to load a project file within SSMS. I also was unable to create new projects. My fix was to reinstall SQL Server 2008 R2.
1 vote -
Fortress - Exclusive Checkout / Object - Lock
Similar to how fortress works with visual studio. All objects in the database would require an exclusive or shared lock to be worked. If an object is changed without a lock it becomes renegade for that user.
8 votes -
Put blue indicators on Object Explorer for changes to static data
I have my database linked to source control, and if I make a change to a schema, it shows a blue dot in the Object Explorer to indicate there are pending changes. However the same does not apply to static data – if I change some data in a table that is setup for static data source control, there is no icon to indicate there are changes to be committed. The data change does appear when I go to the commit changes tab however.
15 votes -
Support for Dynamsoft SCM
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.
7 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 -
Support change data capture (CDC)
When enabling change data capture on a database, source control does not pick up the system tables created, nor the changes to the database configuration. It is only able to gather the schema, role and function changes
22 votes -
Check-in comments to code comment block
Back in Visual Source Safe Days, we had the ability to add a macro to the comment block of our procedures and functions. It was something like $HISTORY$.
When checking in our code, it would add whatever comments we added to the procedure automatically.
7 votes -
Control-backspace in textboxes
A very tiny request: I like to use control-backspace to quickly delete words when typing in a textbox. This doesn't work in the commit message.
4 votes -
Allow linking to system databases
I don't think this suggestion is here already, apologies if it is! I would like to be able to link system databases (esp master) to source control as my company has a number of shared procs here. The ability to optionally exclude the normal system procs when extracting would be really useful.
12 votes -
Incorrect differences shown for data changes
I just did a data edit (inserted one row) but in the differences I see three rows inserted and two removed. Two of the rows inserted are letter for letter identical to the two rows removed.
Doesn't really matter, just a little confusing to read
13 votes
- Don't see your idea?