588 results found
-
bugid
Project management issue tracking software (Gemini, JIRA etc) use BugID to link checkins against issues. This allows for a managers to oversee progress on issues and other things (eg: risk of change, code review etc). The SVN BugID (a checkin property) is how a development code checkin is linked to an issue. Add this, and I can integrate our solutions easier at a CMMI level 3-5
35 votesFor now, enter your BugID into the comment field when you commit changes.
Please continue to vote/comment here if you would like to see a seperate Bug ID box like TSVN has. See James’ comment for more details.
-
Auto complete changed object names in commit message
It would be very cool if this tool would auto complete changed objects in the commit message like TortoiseSVN.
6 votes -
workspace per database, instead of per user account
At current we have SQL source control running in a remote environment. However, a DB - SVN link is stored for each user account, and is not transparent to the other developers.
Worse yet, with each developer having their own workcopy in their local profile, the same data will be duplicated several times. Also: conflicts will arise since each workspace updates on its own, while the DB might already be updated from another workspace.
Therefor: Suggest to keep 1 workspace per DB, to prevent issues of multiple workspaces or repositories linked to the same DB.
10 votes -
12 votes
James Billings
responded
If MKS offers a command-line, you may be able to configure it with config files – see http://www.red-gate.com/supportcenter/Content?p=SQL%20Source%20Control&c=SQL_Source_Control/help/2.2/SSC_working_with_config_files.htm&toc=SQL_Source_Control/help/2.2/toc1432725.htm
-
Scroll beyond teh current page when seleting multiple items
I can select multiple items by click/draging over the items, however it will only allow me to select what is on the current screen.
1 voteDo you have a wheel on your mouse? Once you highlight the items in view, just roll your mouse wheel to keep going down the list.
Another way to do this is to click the first row, hold the shift key down, and scroll down to the last row and click again. This will allow you to highlight everything.
Also, there’s a checkbox in the column header of the Commit/Get list if you want to uncheck/check everything all at once.
I hope this helps.
Stephanie Herr
Project Manager SQL Source Control -
scary stuff when you minimal privileges
I recently connected to my database as a new user with minimal privileges (just data_reader). Later I went to SQL Source control to see changes (forgetting I was logged in as the restricted user) and the output was scary - every SP was marked as deleted and most tables were marked as edited (text replaced with 'encrypted').
I didn't have the courage to hit commit just to see what happened - it was too scary seeing my entire database marked for deletion!
3 votes -
Change btn txt on the 'Get Latest' tab.
Button says Get Latest. Incorrcet Subversion term. SVN Update or something similar will prevent the confusion.
5 votes -
Support SVN "Id" keyword
We already maintain our database scripts in SVN (using Tortoise), and are very keen to change over to your product.
We include the SVN keyword $Id$ in a comment at the top of every object file. When we commit, SVN automatically updates this to provide the Date, Author and Revision number of the last commit. This means that we're easily able to see which version of a particular stored procedure or function is in a client's database.
SQL Source Control doesn't like this though. When I commit a change through SQL Source Control, the Id is updated by SVN, and…
89 votesWe’re currently not planning to support this for v1. Would you be ok to remove the $id$ keyword for now?
We’ll have to see how many votes this suggestion gets…
Internal reference number: SOC-113
-
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.
-
Automatically commit changes as they are made
It would be nice to be able to automatically commit changes in the background when an object is created or modified.
19 votes -
Rename of objects containing [ not working
I inadvertently put [] into lots of my column names and this broke RedGate. Google found something that might help explain:
I eventually fixed it by dropping the tables, which caused RedGate to run a create table statement rather than sp_rename.
1 voteHello,
What do you mean by “this broke RedGate.” How exactly did it break? Did you get any error messages?
Could you email Support@Red-Gate.com the table script that had the [] in the column names and what you changed it to? This will help us to reproduce the problem.
Thank you!
-
Source control for replication scripts.
The ability to maintain replication (scripts) as a source control object.
16 votes -
Bug: commit changes showing no changes
I've just had a stored procedure that I haven't modified come up as having changes to commit. The Previous and Next buttons are disabled as though there are no differences and I can't see any differences. Yet it repeatedly comes up as an object with changes. Huh?
1 vote -
Bug: drop database and then recreate causes conflicts
I have a database managed in SVN. On my development machine I deleted it and then recreated it with the same name. RedGate maintained the link to SVN despite the drop (ok, doesn't bother me) but it then marked every object in the database as being in conflict
2 votesThis is a known issue. I’m glad you’re ok that the link to SVN is maintained. The problem is the underlying working folder is out of date.
WORKAROUND:
Option 1)
On the setup tab, unlink the db from source control. If you still want to manage the db in SVN, then relink.Option 2)
Use the Commit or Get Latest tabs to decide if you want to keep the version in your db and commit it or take the version that is in source control. After making a decision using the radio buttons in the differences pane at the bottom of these tabs, you must then click the Commit and/or Get Latest buttons to actually perform the action.HINT: You can select multiple rows by selecting 1 row and then hitting Ctrl-A or select the top row and then hold the shift key down and select the…
-
SVN Lock mode by default : Impossible to commit
We use SVN with the config ". = svn:needs-lock=*" to automatically lock files on all our repositories (parameter in the config file of SVN on the computer of the developer).
So a source file can be modified by only one developer at a time.
It looks it’s a problem with SQL Source Control because the files in the local directory of the working databases are in read only.
When I commit a change, I have the message “Do not have permissions to modify the file C:\Documents and settings...\Stored Procedures\dbo.PS_select.sql”.
The commit is stopped.
Of course, we would like to…6 votesWe currently do not support lock or exclusive checkouts (lock-modify-unlock model). We are supporting a copy-modify-merge model.
In order to use SQL Source Control, you’ll need to use this model for now until we implement locking/exclusive checkouts in a future release.
To do this, undo the change to the Subversion configuration file, remove the needs-lock property from any file in the repository, manually svn update the WorkingBases directory, unlink and then relink the db in SSMS.
Depending on your OS, related files can be found in:
C:\Documents and Settings\\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
or
C:\Users\\AppData\Local\Red Gate\Logs\SQL Source Control 01) Right click on WorkingBases\\Stored Procedures\dbo.PS_select.sql
and select Properties
*You can find the which corresponds to your db by looking in the LinkedDatabases.xml file.
2) Select the “Subversion” tab at the top
3) Click the “Properties…” button near the bottom
4) Is there a svn:needs-lock property?… -
fails on more than 200 objects
I have about 800 objects. I can only add 100 to 200 objects at one time. If I try to add too many it fails.
3 votesThis sounds like a problem we’ve seen before. Do you have Microsoft Security Essentials installed? If so, this could cause a problem when committing a large number of objects, which is usually the case when first committing an existing database to source control. Your workaround of doing a smaller partial commit seems to fit this expected behaviour.
To get around this, please configure Security Essentials to exclude LOCALAPPDATA\Red Gate\SQL Source Control 0\ from live protection.
-
No whitespace in file/directory names
I want an option for all scripts and directories to have no whitespace in their file names. For example "Database Triggers" would be "DatabaseTriggers". This makes working manually with the scripts from the command line much easier.
2 votes -
Improved object merge support - Provide ability to merge a conflicted object, instead of just Keep Mine or Take Theirs
I have seen no way on how to actually do a merge with SVN and mark as merged etc
We really need a more inutuitive way to merge the changes to SVN and vice versa. At the moment I am getting conflicts that I can't put into SVN because there is no way to say it has been merged, or even how to merge the changes.131 votes -
Foreign Keys scripted in different order each time table is edited
I've found that frequently when I change something about a table (add a column for example), then when I do a diff of that table from SQL Source Control before checking in, the diff shows that the order of the Foreign Keys has changed. For example, it might list FK1, the FK2, and then FK3 on the left side of the diff, and FK2, FK3, and then FK1 on the right side of the diff. The definitions of the foreign keys have not changed, just the order in which they're scripted. So, this is…
3 votes -
TFS integration should allow you to select which workspace to use
TFS integrations really needs you to specify which workspace you are working with. This does wrong right from the start - when I try to link a database to TFS, it asks for the source URI and data folder, but it will only accept data folders already checked in, not that I have created in my workspace.
6 votes
- Don't see your idea?