588 results found
-
Synchronize Replicated Database Environments // or Possible Workaround such as Filter of Table Columns, contraints, indexes, etc...
Create a way I can synchronize:
- NON REPLICATED database X REPLICATED database
- REPLICATED database X REPLICATED Database
Ability to syncronize tables/columns, views, sps, triggers, functions, indexes and constraints.
Avoid displaying individual constraints used for replication. E.g. Constraints that use range of IDs, Indexes of merging, etc.== OR ==
Allow me to:
- Filter Table COLUMNS by Name or part of it; E.g. 'rowguid', '% column name %'
- Filter Constraint Name or part of it; E.g. 'replidentity%'
- Filter Index by Name or part of it; E.g. 'MSmerge_%'
61 votes -
Ungroup Source Control Commenting
Is it possible for the comments window to hold a comment per object rather than as a group? That way I can quickly individually comment multiple objects and check them all in in one go.
6 votes -
The ability to call source control features in a batch command respective with a command line tool
We are looking for the ability to commit a set of databases periodically (e.g. nightly) into SVN. So we have a fall back if someone forgot to commit and loose changes on important databases.
2 votes -
Make the ALL checkbox under "Get Latest" work so I can de-select everything
Make the ALL checkbox under "Get Latest" work so I can de-select everything. It seems to only work when selecting all items.
1 vote -
Allow sorting Commit Changes by multiple columns (e.g. Type then Name)
I would like the option of sorting by more than one column at a time in Commit Changes. I typically want to sort first by Type and then by Object name.
4 votes -
Include miscellaneous options / database properties
SQL Source Control tracks options like Default Collation. It would be useful to extend this to include all options that can be configured e.g. Recursive Triggers.
6 votes -
Needs to be faster when retrieving changes. It takes forever to bring back the list of changed objects after you make a commit. I
Needs to be faster when retrieving changes. It takes forever to bring back the list of changed objects after you make a commit. I have to make multiple commits at a time, some are single items some are multiple items. Each commit is based on a change set developed in TFS. It takes all day to get through 88 items just because of the time it takes to refresh the list.
Use a rolling refresh of the list after the initial load, new objects can be added in the background, those that are committed just get dropped from the list…27 votes -
Screen Reader Access
Can you make the tools more accessible through screen reader?
The Tools are not readily accessible through Screen Readers and thus are very difficult to use by partial sighted people who rely on screen readers. I am one of them.4 votes -
I just installed a "minor update". If it is minor, why are you prompting me to read a 19 page, 7,500 word licence agreement?
Only display changes to the agreement and stop wasting my time.
4 votes -
Migration Script Rollbacks
The only obstacle I have with switching to SQL Source Control 3 as a complete solution to source controlling and deploying is its inability to rollback custom code in a Migration Script. I would like when creating a Migration Script the ability to create a Reverse Migration Script so that if I use SQL compare to roll a code push back to a previous version in source control, it will grab the reverse script the same way as it grabs the migration script currently when pushing.
For example, if my migration script has an update statement in it to modify…
94 votesAs we noted in https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2299881-migrations-support-for-git-mercurial, we have stopped work on Migrations v2 beta.
Unfortunately, there are currently no plans to include migration script rollbacks alongside the forward migration scripts, but we are still watching this request with interest.
-
Red Gate Source control should only need one workspace
Red Gate Source control should only need one workspace. Is there a specific reason Red Gate creates multiple workspaces per database linked? This is creating a mess of my workspaces.
58 votes -
4 votes
-
Copy history comments in SSMS
When I am updating my database objects, I'd like to include the version history in my script. I can't copy the version comments into my header block. Perhaps a SQL Prompt like a snippet that pastes the comments into the text editor would work.
1 vote -
Button to script changes, but not commit them
This is similar to "Allow commits to occur with other code changes," except that if I link to a scripts folder, I have to do that all the time, and I can't ever just commit. I'd like to have the option to commit if what I'm doing is purely in the db (a sp change, for instance), or to just script to the folder if there are application changes also required (like adding a table column)
2 votes -
Sort constraints / indexes by name
it would be nice to have the constraints sorted by type and name in the table scripts (this one that are checked in to SVN and are used to show me the differences)
Example: I have a table with 11 FKs which I will see as
ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk4] FOREIGN KEY ...
ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk3] FOREIGN KEY ...
ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk6] FOREIGN KEY ...
ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk7] FOREIGN KEY ...
ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk5] FOREIGN KEY…5 votes -
For 'Commit changes' the button to refresh is on the far right. For 'Get latest' the button is on the far left side of the window.
Consistency is king. Having the buttons always at the same place makes it easier. So, either you have both refresh buttons on the far right or on the far left side of the window. I personally prefer the left side as this is closer to the tabs. But that's just me.
4 votes -
SQL Source Control Static Views (or Table Subsets using WHERE clause)
I would like the ability to source control a subset of a table (perhaps using a view).
I have inherited a database where lookup data is intermixed with user defined data. We reference the lookup data in the table using a code (VARCHAR) that is unique when another field is NULL, so it is possible to ensure that records are created/updated/deleted without concern for the primary key involved.
For more information, you can refer to this forum post:
http://www.red-gate.com/messageboard/viewtopic.php?p=50087636 votesHi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.
With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.
SQL Source Control introduced pre- and post- scripts in v6.3.
A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data
If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.
SQL Change Automation:
- Supports column filtered static data tables in the SCA plugin in SSMS
- Supports multiple post-deployment scripts, in case there is…
-
Functionality after restore from command
After we have run a restore database command, the source control do not notice, that some, earlier loaded stored procedures from lastest version are after that newly out of date.
Source countrol should recognize a restore and scan completely new for the latest changes.4 votes -
5 votes
-
Commit from query editor
It would be great to be able to commit a change directly from within the query editor window. For example, right click within an 'alter procedure' statement, for example, and then 'commit change'. A dialogue box would allow a comment to be entered, and then the commit would take place in the background.
This would give a very quick workflow for doing commits without breaking out into a different UI.
14 votes
- Don't see your idea?