Cambridge UK, 2 June 2016 – In modern software development, source controlling applications has become standard practice. By employing source control, changes can be tracked and rolled back, errors avoided, and Agile techniques followed. SQL Source Control brings the same advantages to databases, and the latest version finally overcomes a crucial challenge so that databases can be included as a full partner in the development process.
Launched in 2010, SQL Source Control is a plug-in for SQL Server Management Studio (SSMS) that links databases to application version control systems. Using the industry-leading comparison engine from Redgate Software’s SQL Compare, it has helped thousands of development teams improve their processes by applying the concepts of application version control to database development.
Recent updates to SQL Source Control have included enhanced Git integration, significant performance improvements, object locking, and support for SSMS 2016 & Team Foundation Server 2015, all of which have enabled users to stay in sync with their team. One factor, however, has lagged behind: data.
While changes to the code behind database schemas can be tracked with SQL Source Control, any changes which involve data have been a significant challenge. If moving data around is an essential part of the change, for example, then due to the changing landscape of the database world, there have still been obstacles to overcome. Until now.
Version 5 of SQL Source Control gives users a simple, repeatable way of creating migration scripts that includes handling changes to data, committing those changes, and using them in database deployments.
Regular schema changes which can be safely handled by the SQL Compare engine are added to ‘compare blocks’ and are used in the automatically generated deployment script as normal. Changes which involve data are written as migration scripts and added to ‘migration blocks’. At the deployment stage, the blocks are deployed in the order changes were made, so users can be sure the deployment accurately reflects the development process.
As Elizabeth Ayer, SQL Source Control Product Manager, says: “This release means the bedrock of version control can now be applied to virtually every database development process. It allows you to use existing branch practices, adopt whichever version control system you prefer, and do migrations as well.”
An increasing number of organizations are exploring and using the principles of continuous delivery in their application development, and SQL Source Control v5 now allows the database to be included.
“If you’re considering database automation, where the absence of migrations has been a showstopper,” says Elizabeth, “this is the release that really does make it possible to automate database delivery.”
Steve Jones, DBA and Microsoft MVP concurs. “I’m thrilled by the changes in SQL Source Control. Enhanced support for version control systems such as Git, and the improvement to migrations scripts have changed everything. This is something to get really excited about.”
With the new migration script feature, users have complete control over how changes are handled, making it possible for every team member to get the latest changes from source control without the risk of losing data.
Elizabeth Ayer concludes: “Making database development as easy as application development has been our goal for a long time at Redgate. With SQL Source Control v5, we’ve now succeeded.”