SQL Source Control
Thank you for evaluating SQL Source Control. Your feedback will impact what we do next!
-
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 -
On conflict when commiting changes able to right click and open proc/table in new sql editor
When you get conflict when commiting changes it would be nice to be able to right click and open proc/table in new sql editor, do you change (merge) and continue.
14 votes -
Step 4 takes a very long time since I upgraded to 3.1.0.5208.
Seems that since the release of SQL Source Control 3.1.0.5208 step 4 has been taking a very long time. I don't know if this is just my set up or is happening for everyone. Also, if I try to do a dedicated database development then step 4 never finishes.
26 votes -
Add button Stop/Start Checking for modifications
Sometime I work with proxy of my customer and my DB, linked to source control, can't connect.
Please, I need a Start-Stop button to stop the connection with the source control in this situation. Thank you.4 votes -
Exclude/Include filter not working as expected, SLOW performance
we have 13000 objects in our database.
12800 of them are all in the dbo schema which contains the standard logic for our product.
The rest 200 are in the customer specific schema.
We are not interested in source controlling the standard logic, since we get it from our supplier.
We need to source control our customer specific changes. For that every change is made in another schema.
We can perfectly filter the objects out for source control with your tool.
(so they do not appear on the commit screen). However it is very very slow, that's why I suspected…5 votes -
Auto link source control to repository
My use of Source Control is in its infancy, but it would appear that when you commit your changes to Source Control, an entry to your repository (for us its TFS) and the version number. From what I understand this is only used by the compare products. But why can't this link be used by Source Control to automatically link others to the same repository?
12 votes -
SQL Doc - Rename or remove server name
When generating documentation in SQL Doc it would be nice to either rename or remove the server name. If I'm generating documentation for a client, for example, I would rather they not see the SQL Server name and get confused.
6 votes -
sql source control window resizing
When resizing SSMS, the SQL Source Control window does not resize correctly. Some UI elements appear on top of others. Not a major issue but is likely not working as expected.
1 vote -
Buggy feature with Mercurial, maybe other source control systems too.
When I update to a node in a branch that is not the head of the branch, for instance to rollback my database to a previous tag. The moment I hit the get latest tab in SQL Source Control, it automatically updates to the head of my branch, making it impossible to revert to a previous version.
1 vote -
Intellisense when typing table with underscores (My_Table)
I have a table called My_Table.
I should be able to just type "mytab" and have Sql prompt recognize that as an option in intellisense, like devart SQL Complete does. Currently, it gives me no suggestions.
3 votes -
get latest from source control - dependencies
After you click the "Get Latest" button, while the "Determining schema changes" step is processing, there is a dialog that will sometimes pop up that says "Get latest from source control - dependencies". The "affected objects" list does not include the schema name for these objects. For databases that make heavy use of schema names, the schema name is critical to display here.
1 vote -
The toggle button functionality
I have version 3.2.0.27. When you have conflicts, the toggle button at the top of commit and get latest won't uncheck items that SQL Source decides to check. I have to select all the items and then click a box to uncheck, then check the ones I want. If I don't want to resolve the conflict yet, it's not ideal.
10 votes -
For shared development environment, replace "GET ALL" with list of historical changes made
When developing in shared enviroment, I'd love a history tab that I can review all revisions with details, and not have to have a modal window separately. I believe this should be integrated into the main source control tab as change history log. This could help make others aware of changes made that could affect them, yet were already committed. Thanks!
4 votes -
Allow objects to be committed without their dependencies
I am working on a project that is an enhancement to an existing database that is controlled by an external party. I am referencing objects that I have no control over via foreign keys, presently I cannot commit the foreign keys to source control unless I also commit the dependent objects. I do not want to commit these as I do not control them.
Would it be possible to have some mechanism that permits me to commit my changes without the dependencies, something like an override checkbox for the default behavior that will also place messages in the notification box…
3 votes -
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 -
When opening SSMS show all databases with differences in the Object Explorer view without having to select each individual database
When opening SSMS highlight all databases with uncommitted changes in the Object Explorer view without having to select each individual database.
1 vote -
SQL Source Control 3.1.0.5208 Failure to load Add-on to SQL Server 2008 R2
This is actually a defect in the product. After upgrading to 3.1.0.5208 of the SQL Source Control, the Add-On for SQL Server 2008 R2 no longer loads. I had to revert to using 3.0.13.4214
5 votes -
Accomodate for people with colour blindness
One of my colleagues has colour blindness.
The distinction between a non-reviewed database (the grey circle) and a database with outstanding changes (blue / white icon) is difficult to see because of the fact that the icons are so small (the less pixels to compare, the harder it is by all accounts) and often can be far away (i.e. if there are other non-source controlled database between them on the database tree in SSMS).
It would be helpful to make a clear distinction between the icons - either make the grey icon a flat colour (i.e. remove the highlight within…
5 votes -
Cannot Get Latest
Everytime I try to Get Latest I get the following....
System.Exception: Failed to update to the head revision after 10 attempts ---> System.Exception: Failed to update to the head revision after 10 attempts
at RedGate.SQLSourceControl.Engine.LinkedDatabase.GetDatabaseFolderWorkspaces(ICancellableOperationStatus status, IScriptFolderStructure scriptFolderStructure, IReadOnlySourceControlServerCallBacks callBacks, SourceControlRevision& revision)
at #GWeb.#WXM.#Fieb()
at #GWeb.#Wheb.#tieb(Func`1 )
at #GWeb.#WXM.#8ZW(Boolean )
at #GWeb.#XXM.#yRW()
at #GWeb.#WXM.#qYM()
at #GWeb.#XXM.#iS()
at #qlhb.#0heb.#l36(String , #1heb , ICancellableOperationStatus )
at #qlhb.#K3c.#83c(String , #O9U , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#A3.#eL5b(ICancellableOperationStatus )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#jzb.#Qnw()
--- End of inner exception stack trace ---
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#VAb.#xSXc()
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#uz2b(String , IDatabaseConnection , #1heb , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action ) …1 vote -
On shared mode, Source control sync delayed issue
Shared mode is perfect for small team DEV environment, but status update delayed to sync is annoying....is there a way to config the sync frequency?
3 votes
- Don't see your idea?