588 results found
-
Need to disable Source Control.
Need to disable Source Control. It causes way too many errors and slowness. I only actually need to use it once every 2 weeks when we commit our work, but it runs all the time, and causes a lot of frustration.
30 votes -
XML COMPRESSION
SQL Server 2022 (and now Azure SQL) includes support for XML compression. Unfortunately, this option is not recognized by SQL Source Control (or SQL Compare), so when XML COMPRESSION is turned on for a table and that table is saved to source control, the XML COMPRESSION option is not saved to source control.
29 votes -
Allow include Identity option at table level instead of Database level.
In many databases there few tables with static values which are mapped with enums in the code. For such tables, Include Identity columns option is required. However, for few tables, we may not require to maintain the same primary key value in the source and target DB. Please do the needful
29 votes -
Import/Export settings
I had to recreate a user profile and AppData\RedGate folder copy did not retore linked databases cleanly. Would like a method to export settings for use with profile recreation, sharing with other team members, backing up configuration before making changes.
29 votes -
Source control slow down
SQL Source control is slowing down my entire SSMS. This wasn't always the case, but now trying to get a context menu to show up on a table can take up to 30 seconds. Please fix!
29 votes -
Would love to see a feature that ignores any local changes and allows you to simply bring the local database up to the latest version
We often restore databases into our working folder and would love an option to simply bring that database up to the latest source controlled version. Right now when we restore a database Source Control thinks we made a bunch of changes so we end up having to "undo" those changes.
29 votes -
SQL Source Control support SQL Server maintenance jobs
It would be mint* to be able to have SQL Server Maintenance jobs included in SQL Source Control. Could it be added as a new feature?
- (see kid from Super8 movie)
29 votes -
Change the icon in ssms for the tables that are linked as static data.
When you link a table as static data in Sql Source control it would be nice if the static tables were easily identifiable under the tables node in management studio.
28 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 -
Add "if exists...drop" option for programability objects
Not everyone will want to use SQLCompare for continuous integration for various reasons. Adding an option to include an if exists...drop statement with certain types of objects means that all scripts can still be CREATE scripts while allowing for other CI implementations.
27 votesFor now, you may be able to use a batch file that executes SQL and drops the objects you want re-created before using the SQL Compare Command Line API. Since the objects are dropped, the synch script will generate CREATE scripts instead of alter.
If you wanted to create everything from scratch, you could drop and recreate the database, which would generate all CREATE scripts.
I hope this helps for now.
-
Indication of current server / database in source control pane would be useful
When you select a database in the object explorer tree, then click on the link to existing repository in the red gate source control pane, the highlighted database isn't very obviously highlighted (dependin on your colour scheme) because the object explorer no longer has focus.
In addition, with multiple databases, it may not be obvious which server the selected database is on.
With the link to subversion repository dialog open, it is difficult to check which database is selected - a problem if you have to link a number of databases on a number of servers, and have lost track…
27 votes -
Implement Source Control for PostgreSql
Can you implement Source Control for PostgreSql?
26 votes -
Link databses using solution or project file
We have a lot of databases. It's very time consuming to link all databases one at a time for every developer. It should be possible to make use of a solution file to link a solution with all the databases, rather then mapping one by one.
25 votes -
Support multiple Synonym definitions that change across environments
Support multiple SYNONYM definitions depending on which server (dev, test, prod) the source is being extracted to.
25 votes -
Improve performance over remote connections
We have a team that works remotely so no local network access to source control, only access over the internet. Sometimes I cannot get latest or commit anything because most of the time the source window is stuck on "Determining latest version". I've let it run for a few hours with no luck. It is a relatively large database with around 2000 objects, 1000 stored procedures which have a total size of 4.3MB text.
A SQL Compare snapshot of this database is 23MB or 6.5MB compressed.
What about having an intermediate service which runs on same local network as source…
24 votes -
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace is simply not accep
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace of the tool is not acceptable.
24 votes -
Option to disable the SQL sp_refreshview command in the update script.
An option that prevents the addition of the EXEC sp_refreshview in the update script.
When updating queries that rely on linked servers and the linked server doesn't support distributed transactions the update fails and is rolled back.
Now we constantly have to manually alter the script by manually removing the EXEC sp_refreshview commands. This our server admins will not enable the DTC coordinator on the SQL servers
24 votes -
Support source control integration with SSMS Solutions/Projects
We have SSMS solutions that contain only our stored procedures, functions, and views. We have these solutions in Subversion repositories and are currently using TortoiseSVN to manage changes. It would be great if this tool (or a similar one) would support Subversion integration with SSMS much like the existing support for Visual Source Safe.
It could be much like VisualSVN but for Management Studio instead of Visual Studio.
24 votes -
Better Git performance
While it is great the SSC supports Git, I have found that when connected to a large repository, SSC can take forever to commit or do a get latest.
I have also noticed that the working base and transient folders can grow quite large as the whole Git repo is cloned into these folders. I have had to periodically go in there and have Git compress it's objects so that I can reclaim some disk space.
I imagine that the performance of SSC is related to the size of the Git repo and I just feel like there is room…
24 votes -
Option to force check for invalid objects before committing
If invalid objects get committed to source control, often others cannot Get Latest until the object is corrected and re-committed. Having an option to check for invalid objects before allowing a commit to proceed would prevent invalid objects from getting into source control in the first place.
23 votes
- Don't see your idea?