SQL Server databases under version control - with a click of a button you can put any of the databases
residing on the "master" development server under source control. When a developer joins the source control group
he can easily get the latest version of the development database onto his machine and from then on work worry-free on
his local copy of the database and focues on development rather than spend the energy on managing database changes.
|
|
Auto-generate database change scripts - instead of struggling to keep track of all the changes
he is making on the local database the developer can focus on doing his work; at any point he can click
on he "Schema Compare" button and xSQLVC goes to work to determine what changes the deeloper has made and
generate the script that will allow him to propagate those changes up to the master server. In addition
xSQLVC also automatically generates the "reverse script" that will allow the developer to rollback the changes
in the future if he needs to.
|
|
Check In database changes – once the change script has been generates the user can add a descriptive title
for the script and "check it in". The check in operation will execute the script on the master development
database and log the script into the database changes history. Other developers that have joined the same
version control group will be able to see and apply those scripts on their local copies of the database.
|
|
Get changes from other developers - xSQL Database Version Control checks with the master server periodically
to see if any one has checked in any database changes; the get latest tab of the application displays the list
of scripts that have been checked in on the master but have not yet been applied to your local copy of the database - with
a click of a button the user can apply those scripts and bring his local database up to date.
|
|
Complete history of database changes - xSQLVC maintains a complete history of database changes making it
easy to go back in time and see who changed what when. Furthermore, the users with the right permissions can export
the scripts, modify them, and roll back certain changes if necessary.
|
|
Rolling back database changes - throughout the process xSQLVC not only generates the change scripts
but automatically generates and stores the corresponding reverse scripts so the users can at any time rollback
certain database changes if and when they need to.
|
|
Deploying changes to test and production - not only does xSQLVC keep the team of developers in sync
during the development but it also makes it very easy to deploy database changes to development and production. The ability
to group the change scripts into "releases" makes deploying certain changes to production very efficient - choose the
change scripts you want, export them and execute them on the QA server and/or production server.
|
|