Dedicated model

Last modified: October 1, 2024

This model allows developers to work on their local copy of the database and commit changes to a centralized repository.

When you link a database to source control with the help of the Studio, a local copy of the database is not automatically created. Therefore, you must create it manually either on your local computer or on the remote one.

Setup

Firstly, all developers install dbForge Studio for SQL Server on their machines so that they can all commit their changes. Then, any of them must link the database to version control and make the initial commit. During this step, it is required to specify the dedicated model mode. Subsequently, other developers can get the latest version of the committed database using one of the following methods:

• If developers already have copies of the database, they need to link them to the repository and retrieve the latest changes.
• If developers do not have copies of the database, they must create new empty databases, link them to the same repository, and then get the latest changes.

Workflow

Once all the developers have linked their copies of the database to the repository, the workflow is as follows:

• Get the latest changes from a version control repository to a database
• Make changes to a database
• Commit changes to a version control repository

It is recommended to get the latest database version before you start working on changes. This should be done to prevent conflicts with others’ modifications.

History

The repository contains all changes made to the database objects. For more information about the history of changes, see View Source Control history.

Conflicts

The changes made to the same object by several developers may lead to a conflict. For more information about how to resolve conflicts, see Resolve conflicts.

Benefits

• The chance of accidentally overwriting changes made by other developers is low because each developer works in an isolated environment.
• Developers can make complex modifications to the database. Even if these changes impact other parts of the database, they won’t disrupt the work of other team members.
• All changes made by developers are easily visible, enhancing transparency and collaboration.

Drawbacks

Developers must maintain databases on their machines, which might be considered a drawback in terms of management and resources.