588 results found
-
Global Filter by Schema should exclude Schema Object with same name
This filter should exclude an object with a schema that has a matching name.
-- All Objects
Exclude where (@SCHEMA = 'tSQLt') OR (@SCHEMA = 'SQLCop')
Did not exclude this schema object definition.
-- Schema
CREATE SCHEMA [tSQLt]
AUTHORIZATION [dbo]
GO3 votes -
Add a "Covered by Migration Script" option to the commit tab
When committing changes it would be nice to be able to mark changed items as "Covered / Included in existing migration script" so that they are not checked into source control. I am specifically talking about uncommitted schema changes. For example, transferring a table to a different schema. SQL Source Control sees this as a drop (from old schema) and create (in new schema), but there are times when it should be an ALTER SCHEMA statement in order not to lose the data from the table. The ALTER SCHEMA can be added to an existing migration script instead of creating…
12 votes -
Support Azure Active Directory Authentication
This has over 50 votes but its in SQL Prompt. This is a HUGE pain for us as we need to use AD to adhere to security policy.
https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/15008409-add-support-for-azure-active-directory-authenticat285 votesThanks to everyone for submitting feedback on this in the form of both voting and comments.
Currently, SQL Source Control does not have strong support for Azure SQL Database: as folks have noted in this item, AAD support, particularly with multi-factor authentication, is desired. Currently SQL Source Control does not work at all with Azure SQL Database with MFA enabled.
An additional issue worth mentioning is that pains with SQL Source Control performance may be worse than interacting with Azure SQL Database due to latency.
We would like to improve the user experience and support for Azure SQL Database, and doing so almost certainly involves addressing both of these issues. This is an area we are beginning to investigate more fully.
-
Decrease size of UI on HiDPI/4K displays
If you have a HiDPI or 4K display, SSMS is scaled to 2x. In SQL Source Control, The Commit and Get Latest tabs are fine, but the Migrations, Locking and Setup UI are scaled MUCH larger than 2x. I would prefer those UIs be scaled to 2x.
7 votes -
Make columns resizable on Migrations tab
It is not possible to resize the columns on the Migrations tab. This makes it difficult knowing which objects to include when creating new migration scripts as most of the names are truncated.
1 vote -
If I exclude items from source control they should not default to be committed due to dependencies.
If I exclude items from source control they should not default to be committed due to dependencies. It would be great if there was a setting when items are excluded to never include them in the list of items that are dependencies.
14 votes -
Locking/unlocking functionality
Get rid of the option for anybody to unlock an object, but instead allow to unlock only by the person that locked the object or by a group in group role in the database where only few people have access.
8 votes -
From the Source Contol tab, it should be easy to tell which instance you are updating.
Sometimes I'm connected to multiple instances and it would be nice if the Source Control tab made it clear which instance I was about to change or commit from.
8 votes -
history
SQL Source Control needs a history view, to be able to view historical Commit/Get updates. A simple list of when/who etc then the ability to see the script used?
6 votes -
Support unicode characters in data scripts Arabic for example
When linking static data to source control the unicode characters are appearing as question marks
so please add the support for the unicode characters in the script files10 votes -
Enable merge button also on "unresolvable conflicts"
Merge conflicts cannot be resolved if both users commit and one of them pushes.
To reproduce this behavior:
1) user A performs a change on a line of a SP
2) user A commits and pushes
3) user B performs a change on the same line of the same SP
4) user B commits
5) user B tries to pull and a message says conflicts must be resolved outside SQL Source Control and it is also impossible to push (please see the attached screenshots)Only if user B performs step 4 after step 5 it is possible to see the…
3 votes -
Track changes as Git does / Support Git reset --soft
It would be really nice if SQL Source Control allowed commit undo like git reset --soft or tracked the filesystem as Git does instead of tracking commits.
Scenario that highlights this unexpected behavior:
- perform some changes on the DB
- commit changes
- perform a git reset --soft from command line (undoing the commit while keeping changes on the DB and file system is not possible from the SQL Source Control UI)
- if further changes are performed from the UI it is possible to commit current changes (old + further changes), but if SQL scripts are changed directly,…2 votes -
3 votes
-
Auto-refresh the changes to commit icon
The blue circle indicating changes to be commited should auto-refresh (added/removed when necessary) and refresh when the SQL Server refresh icon or menuitem are clicked.
Now it only refreshes when the user goes on the Commit or GetLatest tab.
5 votes -
Cannot create migration script for selected changes in the newest version
Using the latest verrsion I cannot create a migration script for selected changes (checkins in the versioning control system).
The menu option it had in the database context menu is missing.
Why did you remove this feature?
It was nice for allowing migrating environments that you cannot connect to.33 votes -
Integrate Get Latest in SQL Source Control With DLM
When doing a Get Latest in SQL Source Control, if database is registered in DLM, then register the known schema from SQL Source Control
1 vote -
Using Powershell to generate/checkin Migration Scripts for each changeset/commit
We are unable to use SQL Compare to deploy Migration Scripts to all of our environments and simultaneously maintain commit level control over what does or does not get deployed to each environment for each release, especially with the high volume of changes and the number of last minute changes to release choices in the final stages of release planning. The amount of manual review of the final deployment script is unsustainable.
Using Powershell, we would like to auto-generate Migration Scripts for each Commit/ChangeSet and Commit those Migration Scripts to TFS. This would allow us to modify the content of…
4 votes -
Strangely "Last changed by" is incorrect.
I modified 10+ tables by dropping and creating an index. On two tables the index didn't exist and I had to create it. Big was my surprise that those two tables had a different user than me set as the owner of the change. It is even more strange that each table has a different user mentioned as the change owner.
No big issue, but still something weird. And perhaps better if the change is linked to the user doing the change.
4 votes -
Add "Select Object in Object Explorer" in Commit changes tab
Add option like SQL Search application for quick acces to object
16 votes -
Separate triggers from tables
Please give option for DML trigger changes be tracked separately from tables. It's very annoying trying to support and enhance a trigger-heavy inherited database that needs an extensive trigger optimizations. It doesn't allow me to isolate and rollback my changes very easily ... and branching and integrating - ha! This was almost a big enough deal to send me to ApexSQL... alas, I am regretting my decision these days. It seems people have been requesting this feature in Source Control and Compare for a while... please stop pushing it aside - it's frustrating. Thanks
77 votes
- Don't see your idea?