Procedures to hookup SQL Source Control to existing SVN

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Procedures to hookup SQL Source Control to existing SVN

Postby carpentercraig » Fri May 23, 2014 1:00 pm

How do we go about setting up links to an existing SVN repository for the SQL Source Control -- in a shared manner? I keep hitting the block of the error message indicating 'folder not empty'

In a shared model - when would the SVN folder ever be empty?
Posts: 7
Joined: Wed Mar 05, 2014 4:24 pm

Postby james.billings » Tue May 27, 2014 8:39 am

Shared model refers to the database being shared, rather than the svn repository- however you're right that the folder won't normally be empty once the first user has linked up.

The normal process when getting started with SQL Source Control would be for the first user to link to a new empty folder in SVN and commit everything. Other users would then link to the same place and will also be able to commit changes. The folder doesn't need to be empty for subsequent users because we add an empty file (called RedGate.ssc) to the folder so we know it's used by SQL Source Control.

If you're trying to link for the first time to an existing set of scripts (perhaps created by SQL Compare) then you'll just need to manually create that file for it to work. If the contents of that folder weren't created by our tools, then you may be linking to the wrong place though.
Posts: 1122
Joined: Wed Jun 16, 2010 10:10 am
Location: Red Gate

Return to SQL Source Control Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests