588 results found
-
Git worktree support
I would like to see support for the git worktree feature. We often need to work on multiple branches at the same time, and this would help.
I see someone else has also asked about this as a feature on your forums. (https://forum.red-gate.com/discussion/86826/is-it-possible-to-support-git-worktree-feature-for-sql-source-control)
2 votes -
Allow git clones from the SQL Source Control UI
Hi - we use git in Azure DevOps. I have a few options for cloning,
- command line (which tbh i dont use much),
- 'git gui' - which is reliable and easy
- clone using visual studio from azure devops which doesnt work too much.
it would be nice to be able to do the clone from the redgate sql source control GUI though
ALSO
When linking the database it would be nice to have a shortcut to
c:\users\username\source\repos - this is where visual studio seems to default to and is a pain to browse to each time.
7 votes -
multiple post deployment scripts
for a number of databases we have a lot of post-deployment steps - basically to add conditional data to tables (that cant be solved by table linking) or adding SQL Jobs.
Currently this can all be thrown in a post-deploy script, but this makes it monolithic and much harder to see changes in objects.SQLCMD syntax would solve this problem (:r .filename.sql), but even executing everything in the post-deploy directory in alpha order would make the post-deploy much more manageble
10 votes -
Refresh-Bug: Locked objects are not notified on other computers
I have found a bug that should be fixed to improve teamwork.
These are the steps to reproduce the bug I found:
Case 1
1. Lock a DB object on machine A with user X
2. Watch the DB object in machine B with user Z
3. ☹ The locked-Icon does not apper on machine B (I have set the indicator update time to 5 seconds)Case 2
1. Modify on machine A the locked DB-Object
2. Execute the stored procedure
3. 😊 The modified and locked icon does appear an machine BCase 3
1. Modify on machine A…6 votes -
Option to ignore replicated objects
Would be good if there was a checkbox to ignore replicated objects. If in the context of the DB (without going to the [distribution] database) you can't tell which objects are replicated, then at least an option to exclude the transactional replication spMSins%/spMSupd%/spMSdel% procedures without having to explicitly add them to the filter.
1 vote -
Add ability to Merge Static Data
"Take theirs" and "Keep mine" are an all or nothing option, I would like to have more control over this and be able to keep my new records but take the updated, or keep my updated records but take the new records, for example.
19 votes -
Implement the "IGNORE" rules so that database objects can be completed filtered out of source control
Introduce something similar to the "IGNORE" rules found in your Schema compare for Oracles solution to the SQL Server Source Control product.
The problem that exists for those of us with third party databases that have 10's of thousands of objects is that they are not workable using this product because it ONLY applies the filter AFTER it has already tried to extract and manage the ENTIRE database. The "IGNORE" option would allow us capabilities similar to filter but they would be applied UP FRONT and BEFORE the system ever tried to gather and manage every single object in the…47 votes -
Bug: Scripts for objects with extended properties full of garbage
When adding an extended property to any table that contains non-varchar or -nvarchar extended properties, three lines of junk code are added to the bottom of the object script file for each of those extended properties (declaring a variable, setting that variable with a select, and a GO).
I believe that this may be related to an issue in the Compare engine that I already opened here https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/39729406-more-efficient-scripting-for-non-varchar-nvarchar — it's really beginning to seem like Compare and Source Control aren't usable unless your database modelling follows the pattern that Redgate expects. I don't think it should be that way round…
3 votes -
Offer an option to right-click on a SQL server instance and link all databases to Source Control
Instead of having to address each database separately to link to SOC, why not have an option on the SQL Server instance to right-click and "Link All" databases in one fell swoop.
We plan to implement SQL Source Control and hundreds of databases need to be linked to SOC. We have been directed to some Powershell options which are supposed to link all databases automatically but that option is not working at our installation2 votes -
Tie multiple task IDs to one commit
We use SQL Source Control with TFS. It would beneficial if we could tie multiple task IDs to one commit and all changes would in one change set.
3 votes -
Add server name next to database name on Commit and Get Latest screens
Have the server name of the database (I.E. DEV, TEST, PRODUCTION, etc.) displayed to the right of the database name.
12 votes -
SQL Source Control search filter
Create a search filter for SQL Source Control, we can have hundreds of objects in our source control, it would be great if you could search by object name and within the objects themselves on a search filter.
6 votes -
snowflake
Add snowflake support
99 votes
Kendra
responded
As David mentioned in the comments, we currently recommend Flyway to help version changes for Snowflake.
Flyway doesn’t help with authoring or scripting changes, but it does provide a framework and guidelines to consistently version your changes in a deployable fashion that’s suitable for automation.
https://flywaydb.org/documentation/database/snowflake
Thank you for the suggestion and comments, as well those who have voted.
-
Include SQL Change Automation (without CI parts) in to replace retired Migrations
From SQL Source Control 7.1.9, the "Migrations" feature has been removed. This is a significant loss. We're told to use SQL Change Automation instead. But that has additional cost - and is only available as the full SQL Toolbelt.
It would make sense to include SQL Change Automation components, but without the continuous integration parts to replace this loss of functionality.1 vote -
Prevent "new version" update banner from hiding the tab bar
After linking a DB to Git, I was trying to get back to the Setup Options that are hidden behind the "Setup" tab/button in the top button bar.
The bar was hidden behind the Update banner. As a new user, I didn't even know that bar existed, so I didn't know that I could get there by clicking the "Remind me later" option, until I had opened a ticket with support5 votes -
Change branches from SSMS.
If you use multiple branches for a database and you need to switch branches there is no way to change branches in SSMS. While opening some UI for git or using the command line is not difficult it would be nice to just switch to some branch, pull and apply changes, as needed/wanted all inside of SSMS
207 votes -
Custom Formatting
Allow for custom formatting used by SQL Prompt to also be used when committing code with SQL Source Control.
131 votes -
Make static data UI sortable / searchable
With 100s or 1000s of tables it becomes quite tricky to find objects in the static data link / unlink UI. Therefore, I suggest adding a search textbox there as well as making the UI columns (name, key, schema) sortable.
7 votes -
add option to view commited deleted object code from repsostiry in SSMS
Currently there is not easy way to see or restore a deleted object that was committed. The object code is still in Source Control - but no easy way to see or restore it using SSMS.
10 votesKendra
responded
I believe that this is achievable by viewing object history in SQL Source Control and then launching SQL Compare or SQL Data Compare to do a diff and potentially restore the prior version. More info is here: https://documentation.red-gate.com/soc7/common-tasks/update-to-a-revision-from-source-control
This does require having licenses for SQL Compare and SQL Data Compare, however, and your suggestion is specific to doing this with SSMS, so I am not marking this as complete.
-
Make SQL Source Control external to SSMS
Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.
18 votes
- Don't see your idea?