Settings and activity
43 results found
-
14 votes
-
3 votes
-
1 vote
-
89 votes
We’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
-
476 votes
Thank you everyone for the suggestions and votes for this over the years.
I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/
I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.
If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment SQL Source Control v1 only supports Subversion and Team Foundation Server. These systems were selected based on polls ran on SQLServerCentral.com, which showed these increasing in popularity over the past 2 years.
We will continue to monitor this site and requests for additional source control systems.
-
6 votes
An error occurred while saving the comment This would be cool! We use SVN here for the development of SQL Source Control and it's such a nice feature...
-
135 votes
Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes
However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.
We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.
An error occurred while saving the comment Thanks for the additional comments...
Jason - The free text area will actually associate the check in (commit) with the Work Item. In Visual Studio, when checking in, you can see all Work Items assigned to you and just select the appropriate Work Item from the list. We plan to implement something like this eventually, but for now, are you familiar enough with the Work Item IDs that you could just type the WI ID in manually instead of selecting from a list?
I hope this makes sense.
An error occurred while saving the comment This is not implemented in version 1, but is very high on our priority list.
An error occurred while saving the comment I'm glad you can use the comment field for now. We're trying to get the basic source control functionality completed first. We are really curious to know how many TFS users need this functionality. Please vote/comment to help us prioritize what features we should work next.
-
131 votes
An error occurred while saving the comment In SVN, I think merging has 2 different meanings. You can merge a branch back into trunk, but you can also merge individual files if there is a conflict (e.g., User1 edited Table1 and User2 also edited Table1 on thier own dedicated dbs. User1 committed without a problem. When User2 tries to commit, he will see a conflict that may need to be merged.) This topic is referring to merge in the second instance where there are conflicts on the same object.
-
8 votes
An error occurred while saving the comment Interesting idea. Would you want the db name in the upper right to be a drop down, or something that you click on and it opens up your dbs in a hierarcy like format? Any other ideas?
-
6 votes
An error occurred while saving the comment Great idea! SQL Source Control currently creates a new workspace in your User's Application Data area and doesn't allow you to specify a worksapce. Therefore, you need to select a folder that has been checked in to TFS when initially linking your db.
The idea is to keep what SQL Source Control does to your workspace completely seperate. Therefore, you could still use your workspace for other things if needed independent of the SQL Source Control workspace. Waiting to see if any other users have any other thoughts or comments on how to best handle this.
-
1 vote
-
3 votes
This 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.
An error occurred while saving the comment Also, do you have Microsoft Security Essentials installed? If so, this could cause a problem when committing a large number of objects. What source control system are you using?
To get around this, please configure Security Essentials to exclude C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\SQL Source Control 0\ or C:\Users\<username>\AppData\Local\Red Gate\SQL Source Control 0\ from live protection.
Please let us know if this fixes the issue.
-
9 votes
An error occurred while saving the comment In SQL Source Control, the database is your working copy. We have not changed the behaviour of SSMS so that you can continue to work directly on your db.
If you made changes to the database, then that's what we would show you when you open the object so you can continue making changes and testing these changes until you are ready to commit/check in the changes. At the bottom of the Commit tab, you can see how your database object differs from the script in source control. This is very similar to doing TFS Compare my workspace to latest version in the source control server. (In SVN, this is like comparing the latest revision to your working copy.)
-
12 votes
An error occurred while saving the comment Hi Renko,
We have another tool called SQL Compare Pro, http://www.red-gate.com/products/SQL_Compare, which allows you to a synch a db to a scripts folder. You can then commit/get latest manually using your source control system.
SQL Compare Pro also has a command line capability (http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Compare&c=SQL_Compare%5chelp%5c8.1%5cSC_CL_Working_With_Command_Lines.htm).
An error occurred while saving the comment Hi Fayez,
In most cases, SQL Source Control and SQL Compare Pro will be compatible. There are some fixes in SQL Source Control that SQL Compare does NOT handle yet.
SQL Compare Pro can read the SQL Source Control format, but SQL Source Control can not read the SQL Compare Pro format. I hope this makes sense. What I mean is, you must use SQL Source Control to link and do the initial commit to source control. Then, you can use TSVN to checkout the database folder to a working area, use SQL Compare Pro to synch to that working area, and then commit using TSVN. SQL Source Control should then pick up those changes so that the latest commits appear in the other db developers "Get Latest" tab if you are working in a dedicated db model.
I hope this makes sense. Please let us know if you have any problems with this.
An error occurred while saving the comment Great idea! This way db changes could be committed in the same changeset as application changes.
You can use SQL Compare Pro to script the database to files and then commit these changes. There is a 14 day free trial on our website at http://www.red-gate.com/products/SQL_Compare. Just select "Database" as the Source and "Scripts Folder" as the target. Once you set this up, you can save the project in SQL Compare to make generating the script files easier the next time.
-
3 votes
Did you know? The “Next” button at the top of the diff pane will jump to the next difference in the script. This may help you jump right to where the first change is for now.
-
1 vote
In a future version, we hope to have the ability to browse a repository so that it doesn’t have to be manually entered. This topic is listed at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/539431-browse-to-a-svn-repository-instead-of-manually-typ.
An error occurred while saving the comment Once you enter the SVN URL, it will be remembered. As you start to type, you'll see a drop down of your previous SVN URLs, so it should be easier after the first time you link a database.
-
7 votes
An error occurred while saving the comment You're right! We don't remember your settings in the early access release. Would you like your settings to apply to both the "Commit Changes" and "Get Latest" tabs or would you like different settings for each of the tabs?
The settings I'm referring to are:
- Show > Text size
- Show > Find - on/off and what side
- Show > Line numbers
- Show > Line differences
- Show > Groups
- Panel height (low, middle, high buttons on the right) -
8 votes
An error occurred while saving the comment I agree that manually removing the brackets would be cumbersome. This doesn't seem to be a problem for tables, but is a problem for stored procedures (and probably some other objects). If the only change is the [], then this should NOT show up in your commit list at all. If there are other changes to the stored procdure, then you will notice these brackets highlighted in the diff pane at the bottom of the commit tab. Once you commit this to source control, the source control version will contain the [] and you should not see these minor differences again.
-
1 vote
Are you still having this issue?
An error occurred while saving the comment Could you email support@red-gate.com a screenshot of the error you received? It would also be helpful if you could include the steps you took before you got this error and your log file.
Log files can be found at C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
Replace <username> with your windows username.
We'll try to work through this issue, but we need more details.
Hmm... We don't have anything like this yet, but I wonder if you could put something together using your source control system's API and SQL Compare Pro's command line, which could be used to update your database from scripts. You would need to update the LinkedDatabases.xml file as well... I'm not sure if this would work... Here's a paper on continuous integration, which may help because it shows how to checkout the scripts folder and then compare and synch this to a db, http://www.red-gate.com/help/Continuousintegration.html.