588 results found
-
Detect disabled indexes
I disable an index on an indexed view and source control doesn't detect the difference, but if I do script object as alter I see the disable line added.
6 votes -
save and load filters
First of all I am very happy with the filter in source control
But is it possible to save and load a filter, I have to set the filter for each server
This will save a lot of work if I have the possibility to save and loadThanks
12 votes -
Save position of comment divider
Thank you for making the comment field bigger. Now, if you could just ensure the component remembers the position of the divider between the comment/header area and the list view below it, that'd be even better. Right now, I have to keep resizing it every time I launch the SMS. Annoying but obviously it can be worked around.
3 votes -
Full Text Indexes cause process to fail
I think the ordering of the build process needs to be addressed. When I get latest on a local machine it looks like stored procedures are being added before the full text indexes they reference. Currently I am having to de-select any referencing objects, apply the full text indexes and then re-select the objects to be applied. Is there any chance this can be addressed in a future patch?
75 votes -
Do NOT show SQL Source Control tab when starting SSMS
SQL Source Control tab should NOT be the DEFAULT on SSMS startup, Object Explorer Details should be the tab selected.
6 votesIf you close the SQL Source Control tab, then it will NOT show up the next time you start SSMS.
-
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.
-
DB level Extended Properties
We have extended properties setup on the database level that currently can't be checked into source control. It would be nice to have that as an option to look at DB level extended properties.
4 votes -
commit changes: Enhance mousewheel in Text Comparison
In the lower panel where I compare the text of different Versions I expect more functionality, when I use the mousewheel, e.g.:
Ctrl+Wheel: Change Text Size
Shift+Wheel: Scroll Horizontally
Ctrl+Shift+Wheel: ??4 votes -
Selectable database in the source control window
Could there be a way to choose which database the source control system is looking at, other than the 'last' database selected in the object explorer frame?
We have several databases on our server, and we cannot explore them/switch between them in the object explorer frame whilst attempting to do something in the SQL Source Control window as it changes the database, and so stops its current action (generally a slow refresh), which is getting rather annoying...
8 votes -
Improve performance over remote connections
We have a team that works remotely so no local network access to source control, only access over the internet. Sometimes I cannot get latest or commit anything because most of the time the source window is stuck on "Determining latest version". I've let it run for a few hours with no luck. It is a relatively large database with around 2000 objects, 1000 stored procedures which have a total size of 4.3MB text.
A SQL Compare snapshot of this database is 23MB or 6.5MB compressed.
What about having an intermediate service which runs on same local network as source…
24 votes -
TFS rollback causes check in error on SQL Source
We got the same, "The list of changes to commit was out of date", error when trying to commit a list of specific objects (table and views). What we discovered is that the list of objects which we were changing were all manually rolled back on TFS the day before. We then went to TFS directly and manually made the changes we were trying to commit via SQL Source Control. We then got latest via SQL Source and made a test comment in one of those objects which we manually checked in via TFS and checked in the test comment…
1 vote -
Connect same database to multiple branches
We use the shared database development model and can have several projects going at once. Some developers may jump back and forth between projects. It would be nice to have the ability to setup a single database connection to multiple branches. Possibly using the SSMS registered server name instead of the physical server name.
39 votes -
Make the Blue Indicator on Database Roles Easier to See
The icon with blue globe under Database Roles is really hard to see. Wish it were clearer.
1 vote -
Invalid object name
Hi,
When doing "Get Latest" on objects which hold non-existing dependencies you get the following error and action fails until you manually identify and deselect the objects or modify the SQL script :
Msg 208, Level 16, State 1, Procedure myl33tprogrammer_proc, Line 4
Invalid object name 'dbo.table1'.Proposing the user to ignore dependencies error messages or to deselect automatically problematic items could improve the "Get Latest" feature and avoid time loss in manual actions.
5 votes -
Add commands
Being able to add our own commands that appear when you right click an object in SSMS.
9 votes -
Prevent user from committing other user's changes
One of the problems with a shared db model, where all developers work against the same database, is that everyone's changes are listed on the Commit List and any user can commit any other user's changes. It would be nice if an administrator setting could be set that would only allow users to commit their own changes There should be someway to prevent other users from committing your changes.
79 votesKendra respondedAn update for users on the status of this suggestion:
An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.
This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.
Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.
We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools…
-
Allow Setup at the INSTANCE Level
Please consider allowing, in a single action, the addition of ALL (or a selection of) databases in a server to the same base VSS location. This would require you to create new projects under the root for each DB and simply auto-commit the changes. Currently, Initial setup on servers with dozens of DBs is quite daunting.
4 votes -
Check in sub-object changes
When working in an Agile environment I will have changes that need to be checked in for the current sprint while still modeling for the next sprint. I would appreciate a way to click on the "arrow" in the source control compare window to commit, for example, 1 out of 3 column changes in the Person table or a line change in stored procedure that coincides with 1 column change and leaving the other lines alone for the next sprint.
6 votes -
Include Linked Servers as a versioned object
We use Linked-Servers to connect to Oracle databases. These objects can be added by a developer and then need to be versioned like any other SQL object.
7 votes -
Allow "Get Latest" in shared model
We occasionally restore a copy of production db over our development db. With SCC in place I imagine it will work like this:
1) Everyone commits dev changes that they care to keep
2) perform restore
3) One person relinks SSC in dedicated mode and uses "get latest" to pull down latest schema to the newly restored dev db.
4) everyone can resume working in shared model.
To cut out the relink in step 3, it would be nice to be able to use the "Get Latest" tab in shared model for occasions like this
34 votes
- Don't see your idea?