SQL Automation Pack: continuous integration and automation for your database

Continuous integration for SQL Server
Continuous integration is not just for application developers. Database code is still code, so the considerable benefits of continuous integration are also available to SQL Server developers. All you need are the right tools.

With a license of the SQL Automation Pack, you can run tools from the SQL Developer Bundle on your build server, bringing your database into your continuous integration process.

Why is continuous integration (CI) best practice for writing code?

• Fixing bugs is cheap - Testing changes up-front means you spot and fix errors early on. Problems don't have a chance to leave your development environment, let alone make it into production.
• Collaborating on development becomes easy - When your code passes your tests, it joins the trunk and becomes available to the entire development team. There's no code waiting to be shared and no painful merges. Instead, everyone can build on each other's work as soon as possible.
• Your code is always working and up-to-date - Only code that successfully passes tests is shared, so you can rely on the trunk working properly. Because code is integrated at once, the trunk always represents the most up-to-date version of the database.

What does continuous integration for databases involve?
Continuous integration for databases involves four processes:

• Ensuring that changes to the development database are in step with changes to your application
• Testing the database creation script
• Testing the database upgrade script
• Testing database code, such as stored procedures, views, and functions

Red Gate tools help with all four.