| Author |
Message |
Bobg
Joined: 29 Nov 2012
Posts: 5
|
 Posted: Thu Nov 29, 2012 9:46 pm Post subject: Link to existing SVN repository |
 |
|
| We have been using Subversion for the past few years for all of our DBs, can SQL Source control 3 be linked to these existing SVN repositories? |
|
| Back to top |
|
 |
james.billings
Joined: 16 Jun 2010
Posts: 840
Location: My desk.
|
| Posted: Mon Dec 03, 2012 4:00 pm Post subject: |
|
|
Thanks for your post.
The answer to this question will depend on the format of the files in SVN - SQL Source Control is designed to work with a certain format of scripts, the same as if SQL Compare had produced them. Assuming this is the case, then you simply need to create an empty file called RedGate.ssc in the root of the SVN folder structure for the DB in question, and then link to that.
If the files are in some other format (for instance a VS DB Project or simply arbitrary scripts) then chances are it won't work unfortunately. |
|
| Back to top |
|
|
Bobg
Joined: 29 Nov 2012
Posts: 5
|
| Posted: Mon Dec 03, 2012 4:41 pm Post subject: |
|
|
| Our respository was created using SQL Compare 8, File, Create Scripts Folder. I created an empty file RedGate.ssc, but get an error when trying to link the database. It says "Path must be an empty folder." |
|
| Back to top |
|
|
james.billings
Joined: 16 Jun 2010
Posts: 840
Location: My desk.
|
| Posted: Mon Dec 03, 2012 4:46 pm Post subject: |
|
|
Using those folders should be OK.
That error sounds like you maybe didn't create the file in the right place, or didn't commit it? It should be alongside the "RedGateDatabaseInfo.xml" file and the various folders containing the objects - in addition, this must be the folder you're trying to link to using SQL Source Control. |
|
| Back to top |
|
|
Bobg
Joined: 29 Nov 2012
Posts: 5
|
| Posted: Mon Dec 03, 2012 6:28 pm Post subject: |
|
|
| Thank you, that worked! |
|
| Back to top |
|
|
james.billings
Joined: 16 Jun 2010
Posts: 840
Location: My desk.
|
| Posted: Mon Dec 03, 2012 6:34 pm Post subject: |
|
|
| Good to hear! |
|
| Back to top |
|
|
Bobg
Joined: 29 Nov 2012
Posts: 5
|
| Posted: Wed Dec 05, 2012 7:41 pm Post subject: |
|
|
| Turns out that when I committed a change to a table it completely broke SQL Source Control. Somehow the scripting routine in SQL Source control added the trigger that was on the table a second time, then complained that there was 2 triggers with the same name. I put in a support request (F0067398) and they told me the SQL Compare is not compatable with SQL Source Control 3. Now I am left trying to repair my repository. |
|
| Back to top |
|
|
james.billings
Joined: 16 Jun 2010
Posts: 840
Location: My desk.
|
| Posted: Wed Dec 05, 2012 7:49 pm Post subject: |
|
|
SQL Compare is compatible, but it may be that version 8 held things slightly differently (although I don't recall this being the case).
If you're able to supply us the relevant original file and details of the change you made, we can attempt to reproduce the problem here to see if there's anything that can be done. |
|
| Back to top |
|
|
Bobg
Joined: 29 Nov 2012
Posts: 5
|
| Posted: Wed Dec 05, 2012 8:06 pm Post subject: |
|
|
| What files do you need, and how can I get them to you? |
|
| Back to top |
|
|
james.billings
Joined: 16 Jun 2010
Posts: 840
Location: My desk.
|
| Posted: Wed Dec 05, 2012 8:33 pm Post subject: |
|
|
Ideally the table/trigger definition (and any related tables/functions that may be required to go along with it) from before you made the change, assuming you can roll back to that.
Then, details of the change you made in SSMS and committed. if you can reply to the ticket you have with my colleague, that would be easiest. |
|
| Back to top |
|
|
|
