Source control and change tracking

Source Control in the header opens a side panel with two tools: change tracking for the database and a Git integration for script folders. Both work with the connection of the active tab.

Source Control is locked in the demo version.

Tracking changes in the database

On the DB changes tab:

  1. Snapshot saves the current state of every view, procedure, function and trigger as a baseline.
  2. Later, Check for changes shows what has happened since: each object as New, Modified or Removed.
  3. Another Snapshot makes the new state the baseline.

That way you can trace what changed even on a shared database, without anyone having to remember to save scripts. Change tracking does not cover table structures; use Schema Compare for those.

The snapshots are stored locally in changetracking.db, not in the database.

Git

Further down on the same tab you can open a Git repository, for example the folder with a project's database scripts:

  1. Enter the path under Repo path... and click Open.
  2. At the top are the branch, New branch, Pull and Push.
  3. Changed files lists new, modified, deleted and renamed files. The checkbox in front of a file includes it in the commit.
  4. Fill in Commit message... and click Commit.

Pull and Push to GitHub need a GitHub token; name and email for commits come from Git author name and Git author email. All three are under Settings.

History

On the History tab, Load DB history shows the change log of all snapshots, Load Git log the repository's latest commits.