This guide describes how to link a database to Plastic SCM using a configuration preset, or to another source control system using an editable command-line template.
Install a Plastic SCM client.
1. In Database Explorer, right-click the database you want to link and select Source Control > Link Database to Source Control.
Alternatively, on the top menu, select Database > Link Database to Source Control.
2. In the Link Database to Source Control dialog, in the Source control repository field, click
.
Note
By default, dbForge Studio automatically selects the repository that was previously linked.
3. In the Source Control Repository Properties dialog, enter the required repository settings:
4. Optional: To verify the repository settings, click Test.
5. To save the settings and close the dialog, click OK.

6. Choose a database development model:
7. To connect the database to the repository, click Link.

The Refresh window opens and displays the progress of the refresh operation.
After the database is linked, it appears in Database Explorer with the source control icon:

If you’re using a system, such as Mercurial that requires a cloned repository folder, follow these steps:
1. Create an empty folder on your local disk to store the cloned repository.
2. Right-click the folder and select TortoiseHg > Clone.
3. In the Clone dialog, specify the source repository, then click Clone.

After linking the database, your next step depends on whether the repository is new or already in use by your team:
In the Local changes section of the Source Control Manager, select the objects you want to add to version control, then click Commit.
For instructions, see Commit changes.
In the Remote changes section, select the objects you want to retrieve, then click Get Latest.
Note
The Get Latest option is available only in the dedicated development model.
For instructions, see Get the latest version.