關於 dbForge Source Control for SQL Server

管理原始程式碼管理系統中的 SQL Server 資料庫更改。

dbForge Source Control is an SSMS add-in for SQL Server database change management in popular version control systems, including Git (including GitHub), TFS, SVN and Mercurial. The tool includes version-controlling database schemas and reference data, perform roll back changes, and maintain the referential integrity of your SQL databases. The tool can also solve other database challenges, including deployment without data loss.

dbForge Source Control Overview

  • Version-control database schemas and table static data.
  • Use either dedicated, or shared development models.
  • Commit and revert changes with dependency awareness.
  • View conflicts and resolve data and schema inconsistencies visually.
  • Track the changes made and detect who, when, and why made them.
  • Plug source control directly into SQL Server Management Studio.
  • Automate database development with DevOps approach.

dbForge Source Control Features

  • Work on a central database or your own local copy - Source Control for SQL Server supports two models for database development, Dedicated and Shared.
    • Dedicated model allows developers work with their own copies of the database.
    • Shared model suggests that all developers work on a single shared database.
      • Regardless of the choice of the database development model, Source Control for SQL Server ensures safe and convenient data changes management.
  • Roll Back Unwanted Changes - The tool allows you to easily cancel any local changes you don't want to commit. Just select the changes you want to roll back the Local changes section of Source Control Manager, and click Undo.
  • Version-control scripts in working folders - A working folder contains SQL script files that represent your database. It allows you to script database changes to a database folder. After saving changes, the database working folder can be source-controlled with your version control system in the same way as you version-control other files.
  • Handle changes in Source Control Manager - Perform essential SQL version control tasks visually in a handy interface, including:
    • Commit. Updates source control with your local changes.
    • Get Latest. Updates database with the latest changes from source control.
    • Resolve conflicts. You can resolve discrepancies between the latest version of an object in source control and the one in local database in two ways:
      • Get Local. Your version of an object will be committed to source control.
      • Get Remote. Your changes will be discarded. The local database will be updated with the latest version of an object from source control.
  • Version-control schemas and reference data - Store and share any SQL Server object and static data. With dbForge Source Control, you can:
    • Link static data to repository.
    • Commit, revert, and get latest static data changes.
    • Handle static data conflicts.
  • View changes history - Look through a full revision history of a database or a certain database object with the Changes History document. You can clearly see the changes made as well as who, when, and why made them.

Supported Source Control Systems

  • Subversion (SVN)
  • Team Foundation Server (including TFS Cloud)
  • Git (including GitHub)
  • Azure Devops
  • Perforce (P4)
  • Mercurial
  • SourceGear Vault