179 results found
-
High DPI screen scaling doesn't work well with SSMS 2016 RC3
High DPI screen scaling doesn't work well with SSMS 2016 RC3.
The source control screen doesn't fill the entire work area, but just takes up a small rectangle in the top left (approximately 50% x 50% of the work area).
This occurs on a 3840x2160 pixel screen, SSMS version 13.0.14000.36, red gate source control version4.4.0.1714 standard18 votesThis problem should be resolved in version 5.8.3, because we’ve changed the UI technology used on the setup, migrations, and object locking tabs.
-
17 votes
This feature is now available as of v1.1.0.19. Please use Help > Check for Updates on the SQL Source Control tab within SSMS to make sure you have the latest version.
Thank you!
-
Source Control bug: Changes to Commit icon
This is a bug:
We recently upgraded source control from 1.x to 3.x.; with the new version the icon that indicates there are changes to commit keeps coming up within minutes after actually doing a commit - and on objects that have NOT undergone a structural change. What's going on? Please fix this.17 votesWe think we have fixed this in the latest version. Please get the latest version from SQL Source Control’s help menu > Check for updates. Please contact support@red-gate.com if you still have issues.
-
Option to store the "Version", "Linked to" and "Migration folder" in a file not the database
Currently Source Control information is stored in database extended properties in the database being source controled. This requires Alter Database. In production those of us who use RedGate for Source Control, do NOT have Alter database because only the sys admins have that. And they do not want to bother with RedGate as they are just acting as auditors not database developers in production. Other environments we have full rights, just not production. It would be great to have an option to store the "Version", "Linked to" and "Migration folder" in a file not in Extended properties in the database.
16 votesSorry that this has taken so long to deal with, but I’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.
This means that as of version 5.1.1 of SQL Source Control, Alter Database permissions are no longer required.
Mike Upton
Technical Lead | SQL Source Control -
Stop offering upgrades as if they were updates.
You software goes out and looks for a update every time it's started and then pops up a little notice. When I clicked on this thinking I was getting an update to my existing software, it installed a new trial version and uninstalled my older licensed version. This is not only irritating, I think it is underhanded and reprehensible.
16 votesThe new update mechanism (the blue bar at the top of the screen) should make it much clearer when your support & upgrades status means you’re not entitled to a major version upgrade, and therefore upgrading would start a new trial instead.
-
object level history
I would like to see history by object. For eg, we should be able to see history for Customer table or Customer.GetOrder sp.
15 votesThis feature is now available as of v1.1.0.19. Please use Help > Check for Updates on the SQL Source Control tab within SSMS to make sure you have the latest version.
Thank you!
-
Require lesser SQL Server permissions than dbo to use
The permission of dbo required to use SQL Source control is not good and indeed a lot of dba's do not like the idea of having to grant dbo permission for users who wish to use the source control. In some companies it would not be possible to grant dbo permission.
Could SQL Source Control be changed to not require dbo but perhaps something lesser. Indeed give the option to not writes extended properties at the database level.14 votesI’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.
This means that as of version 5.1.1 of SQL Source Control, Alter Database/dbo permissions are no longer required.
Mike Upton
Technical Lead | SQL Source Control -
Choose when to calculate static data changes
Our static data tables can have a few thousand rows each. It's costly to have the rows compared every time the SQL Source Control tab is opened to push/pull schema changes (which are much faster to compute). Can the schema and data aspects of this tool be separated to prevent excessive comparisons on data that by nature changes very infrequently.
14 votesThe option to disable data change detection is now available from the Setup tab in the Frequent Updates build, and will be available in the next main version of the product.
If you want to get the Frequent Updates builds, more details can be found at http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates.
-
Support for SEQUENCE object
Sequence object not yet recognized by SQL Source Control.
14 votesSequence objects should have started working from v3.6 onwards – please email support@red-gate.com if you are still having difficulties with this object type.
-
Works very intuitively
Adding a database to a repository and doing the first commits works very intuitively. Great job!
14 votesThanks for your feedback! It’s great to hear! :-)
I’m closing this suggestion so you can have your votes back… -
Commit single changes
I like the ability to right click on a single item and select commit to source control. However, when doing this SQL Source control calculates all of the changes in the database. Can the behavior be changed here to only show the changes for the object selected to commit?
Thanks
13 votesEven though we calculate all the changes, only the object you right-clicked on should be checked. (It should also be scrolled into view, if you have a long list.) Therefore, you can commit just this 1 object.
-
Stop treating Git like a red-headed step child.
GIT seems to always get the short end of the stick. Can't do Object Locking, can't do Migrations, can't do Get Latest, can't View History.
Please stop treating GIT like the middle child in the Brady Bunch. GIT is totally Marsha, not Jan.
13 votesI love your request to much, I’m going to hate to close it as finished soon….
Git is a first-class citizen in SQL Source Control 4.1, which is scheduled to go out within a couple of weeks. You can get it right now if you sign up to the ‘Frequent Updates Channel’ (instructions here: https://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates).
We’ve added Commit, History, Push and Pull (Pull+Apply changes = Get Latest) for Git.
Object locking can be used with Git, but it’s a database-level thing, so is really only useful if you have multiple people sharing a database – a relatively uncommon set-up for Git users.
The latest version of Migrations, in SQL Source Control 5, now supports all version control systems, including Git.
Since that covers every item on your list, I’ll mark this as completed – but thanks for making us giggle too.
Mike Upton
Technical Lead | SQL Source Control -
View "Get Latest" script before execution
It would be beneficial to see the sql script that "get Latest" finally executes (with the option to execute having screen the scirpt) . I have found this very useful in other db sync tools especially if the script fails.
13 votesYou could use SQL Compare Pro and the SSMS Integration Pack to see the script.
If the script fails, then you will have the option to view the script in a query window and you can edit it as needed.
-
Support SQL Server Management Studio 2012
Allow SQL Source Control to work on SSMS 2012, where SSMS 2008 and 2012 are both installed on the same machine
12 votes -
Problem syncing Service Broker items
Have two service broker services that won't synchronise.
Database version shows,
CREATE SERVICE [//DBA/Login-Service]
AUTHORIZATION [dbo]
ON QUEUE [dbo].[Login-Queue]
(
[http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]
)
GOSource control version shows,
CREATE SERVICE [//DBA/Login-Service]
AUTHORIZATION [dbo]
ON QUEUE [dbo].[Login-Queue]
GOWhen I try and commit the changes, it stops at the "Sending Files ..." step and says "Nothing to commit"
11 votesThis has been fixed in v1.0. If you are still esperiencing any issues, please contact support@red-gate.com.
Thank you!
-
Faster way to exclude all tSQLt content
It takes a while to setup all the exclude filters, and this time is worse when the solution to a problem is to unlink and relink. Provide a way to quickly exclude tSQLt content and/or save / restore filters.
11 votesWe provide an option to ignore all T-SQL-T content – you can get to this from the setup tab.
-
Stand-alone app
I'd suggest rebuilding Red Gate SQL Source Control into a stand-alone application (similar to SQL Compare & SQL Data Compare), instead of a plug-in to SSMS.
My SSMS has gotten awfully slow since installing SQL Source Control, even after unchecking the Changed Object & Static Data control options, AND setting EnableObjectLocking to FALSE under the hood.Consider that I'm working all day in SSMS, but I only need SQL Source Control maximum once or twice a day, when committing changes to Git.
Kind regards,
Christof11 votesThe next version of SQL Source Control will be merged into Flyway. Flyway Desktop is a standalone application and provides versioning for over 20 RDBMS. You can learn more about transitioning from SQL Source Control to Flyway at https://documentation.red-gate.com/fd/sql-source-control-164167857.html.
-
Vault 6
Support Vault Server version 6.0 that came out recently. Currently when trying to connect against that version, SSC responds with an error of "unsupported server version". It would be nice to make SSC 3.x work with Vault 6.x.
11 votesSQL Source Control 3.2 works with Vault 6.0 and Vault 6.1. Please check for updates from the SQL Source Control tab’s help menu within SSMS or at http://www.red-gate.com/dynamic/products/sql-development/sql-source-control/download.
If you are still having problems, please contact support@red-gate.com.
-
Support for Source Gear Fortress (Vault Professional Edition)
We moved source control to a product by Source Gear called Fortress. Great Source Control. I would like Red Gate to support this.
11 votesNew EA version 2.0.3, which supports Vault and Vault Pro (5.x versions) is now available with static data and shared model support.
Please visit the following link to download it:
-
Don't show conflicts when working in a Shared (Centralized) DB Model
In a dedicated db model, a conflict will occur when User1 and User2 both make a change to Table1. User1 commits the change successfully. When User2 tries to commit, they will be notified of the conflict. User2 must then decide if they want to take what's in source control or keep their version and commit this to source control. In either case, User2 may need to reapply some changes to the db and re-commit.
In a centralized db model, when all developers are working against the same db, these conflicts should NOT occur.
10 votesThis feature is included in SQL Source Control v2.0, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.
This is a known issue in v1 because the underlying working folder is per user and is NOT shared…
NOTE: Databases linked in v1 default to dedicated databases. You will need to relink your databases to switch development models.
- Don't see your idea?