15 results found
-
Make SQL Source Control Options easier to access
In order to access some options, such as enabling SQL Source Control in multiple instances of SSMS, you have to access a section of the setup tab that you can only get to after you have a database linked to a version control. This kind of thing should be available without having to go through all of that.
As an example of where this comes into play, I open a local DB that I have no intention of attaching to SC and do some work. I then open another DB in another SSMS instance that I do want to deal…
4 votesThe latest frequent update release of SQL Source Control (5.8.0) implements the Global Options as a dialog. You can access it by clicking “Options” in the top right corner. Thanks for your feedback.
-
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.
-
When we do SQL Compare from source control to source control, the URL of our repository appears at the end of the script - can it be removed
When we use SQL Compare from source control to source control, the URL of our source code control repository appears at the end of the script. This is causing security issues for us. There should be a non-manual way to remove this link.
1 voteI am delighted to let you know that this is now released! With Migrations in SQL Source Control 5, the URL to your repository no longer appears.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
-
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.
-
Migrations from Working Folder link
In the "Link to source control" screen there are a number of options.
We use branches, so our working folder is always the most relevant to what we are doing.
When we point the link to the WorkingFolder, everything is great, however, the "Migrations" tab is not available for this type of connection.
This is a pity, because we need to create a migration script that will update the main trunk, when we merge our branch back in.
Please enable the Migrations feature for the "Workingfolder" type of link.
3 votesI am delighted to let you know that this is now released! You can now create migrations scripts even when you’re using working folders.
If you don’t have SQL Source Control installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
-
I have my database objects in an existing SVN Repository, how can I link SSC to that?
We already have our database in SVN, is there a way to access that repository?
1 voteIf you were using SQL Compare to create a scripts folder and source control that in SVN, then you can link your database to this repository. Information is at http://www.red-gate.com/supportcenter/content/SQL_Source_Control/knowledgebase/using-a-scripts-folder.
-
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 -
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 -
TFS Migration script unusable with custom port
When clicking the "Add a Migration Script" link on the Commit Changes tab, the TFS url and port are read only. As we use TFS on port 80 instead of port 8080, we cannot use this feature.
The same applies when setting up the link on the Setup tab.
0 votesMigrations in SQL Source Control 5 no longer requires a separate repository, so you should now be able to use it with your setup.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
-
Centralized uninstaller
I had to uninstall RedGate SQL Toolbelt today, and this involved uninstalling 13 separate products individually. It would be nice if the easy installer could uninstall just as easily.
(So you aren't disappointed that I uninstalled: I was switching over to the MySQL tools.)
54 votesWe now have a centralized uninstaller (this will not work when uninstalling products before they were updated with the new uninstaller)
-
3 votes
There was a bug in the first EA, which caused problems when trying to do the initial commit for large number of objects. It’s now fixed, please get the latest version.
-
Allow option to link to workspace, instead of repos
By linking to a subfolder of an existing workspace and maintaining the copy there, it would be possible to allow an external program to handle the actual commit, and by that including the SQL changes into a bigger revision
3 votesYou can link to a folder by creating a custom config file and leaving the options blank. This will just script out the objects to the folder, but not actually commit them. More information can be found at http://www.red-gate.com/supportcenter/content/SQL_Source_Control/help/3.1/SSC_working_with_config_files.
-
Allow me to specify where to save the Working Bases (e.g., Disk/Drive D instead of C)
The WorkingBases are saved on disk C:\Documents and Settings...”.
To save disk space on C:\, we would like the Working Bases on the disque D:\ (we have databases with more than 5000 procs). Is there a setup somewehere ?47 votesIn SQL Source Control v3.3, you can now configure the location of your working bases. Information is at https://documentation.red-gate.com/display/SOC33/The+specified+path%2C+file+name%2C+or+both+are+too+long.
-
Ability to create a new folder in SVN or TFS when linking a database
When linking a database for the first time, it would be nice if the path selector also had the ability to create a new folder based on the selected database name, so that I don't have to go into my source control system to create the folders.
It would really saves us a few steps if you can automatically create the folders required when linking a new DB to source control. E.g. Tortoise does it just fine in VS. For example, if I specify a path /existingfolder/newfolder when linking a DB, I expect you to create the /newfolder directory in…
26 votesThis feature now appears in SQL Source Control version 2.2!
For more information about the release, please see:
-
Browse to a SVN Repository or TFS 2010 Server Instead of Manually Typing It In
It would be a lot easier if I could just browse to a repository (like windows explorer) instead of having to manually enter it.
21 votesThis feature now appears in SQL Source Control version 2.2!
For more information about the release, please see:
- Don't see your idea?