Tuesday, June 14, 2011

SQL Source Control 2.1

SQL Server developers and DBAs use SQL Source Control to:

  • Source control schemas and data within SSMS
  • Connect their databases to TFS, SVN, SourceGear Vault, Vault Pro, Mercurial, Perforce, Git,
    Bazaar, and any source control system with a capable command line
  • Work with shared development databases, or individual copies
  • Track changes to follow who changed what, when, and why
  • Keep teams in sync with easy access to the latest database version
  • View database development history for easy retrieval of specific versions
SQL Source Control makes database version control seamless. It links your databases to your existing source control system straight from SSMS, so you can enjoy the benefits of source control without having to disrupt your workflow.
It doesn't matter whether your development team works with a central database or individual, local copies – SQL Source Control supports both development models. Just pick the one you work with and carry on as normal.
You can keep track of who changed what, when, and why, improve change management and auditing, and easily share or revert changes. SQL Source Control also stores a complete history of your updates to simplify database versioning, and provides a sandbox for risk–free experimenting.
Because SQL Source Control is powered by our SQL Compare technology, you can even combine it with SQL Compare Pro and SQL Data Compare Pro, to automate deployment and migration of your source controlled database.

No comments:

Post a Comment