SQL Source Control - 2.0

SQL Source Control

Learning SQL Source Control - 2.0

Using the evaluation repository

If you do not have a source control system set up, or do not want to use your existing system to evaluate SQL Source Control, you can create a Subversion repository using the Just Evaluating option when you link a database to source control:

Creating an evaluation repository creates a local Subversion repository. You can use this to source control a database, however local repositories have limitations.

Generally, you are recommended to set up a Subversion server rather than using local repositories.

If your are using an evaluation repository, you can migrate it to a Subversion server, retaining the history. For instruction on doing this, see Moving the evaluation repository to an SVN server

Local repositories are designed to be used by a single user on a single computer. It is possible to share them by giving multiple users read and write access to the repository directory. However, this is not recommended.

If you want to use the evaluation repository under a shared development model, you need to give each user permissions to access the repository directory.

A Subversion server supports the protocols http://, https://, svn://, and svn+ssh:// so it is easier to set up access for multiple users, security can be stronger, connections may be faster, and you have more fine-grained control of user permissions.

For more information, see Accessing a Repository on a Network Share in the Tortoise SVN documentation.

See also

Setting up a local Subversion repository

Setting up a Subversion server

Moving the evaluation repository to an SVN server

Linking a database to source control

Was this article helpful?

Search support
Forums

SQL Source Control

all SQL products

all products