Microsoft SQL Server Continuous Integration

5,235 views

Published on

Presenter: Ernest Hwang of Practice Fusion > This presentation shows how to simplify your database deployments, ensure that no database changes are overlooked, and implement unit tests using the suite of Red Gate developer tools.

You'll see how Practice Fusion streamlines database deployments in their Integration, Testing, Staging, and Production environments. This frees developers from the burden of maintaining deployment scripts, while reducing the number of overlooked breaking changes to zero.

The demo uses a Windows Azure box as the Jenkins (Continuous Integration) server and several SQL Azure databases (representing Integration and QA environments). The entire repository is hosted on GitHub (https://github.com/CF9/Databases.RGDemo), for anyone to download.

You'll learn how to:

* Add your database to source control in under five minutes
* Create a CI Job to validate your database “build”
* Deploy database changes to your environments with a mouse click
* Set up database unit testing using tSQLt
* Avoid problems when implementing Database CI in the “real-world”

Ernest Hwang is a Principal Software Engineer at Practice Fusion in San Francisco. He uses Red Gate SQL Source Control, SQL Compare, SQL Data Compare, and SQL Test to automate Practice Fusion's Continuous Integration efforts and instrument database deployments.

Published in: Business, Technology
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,235
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
78
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Microsoft SQL Server Continuous Integration

  1. 1. SQL Server ContinuousIntegrationUsing Jenkins and Red GateErnest HwangPrincipal Software Engineer, Practice FusionPresented to theSilicon Valley SQL Server User GroupMay 2013
  2. 2. Who am I?• Ernest Hwang, Principal Software Engineerat Practice Fusion in San Francisco• C#, .NET, SQL Server Developer• Working with SQL Server since 1999 (SQL Server 6.x)• Using Red Gate for Continuous Integration since June2011• Someone who got tired of maintaining a folder ofdatabase scripts for every release.
  3. 3. Why am I here?• To show how easy it is to apply CI principals toDatabase Development
  4. 4. What’s this?A “How To” guide for automating your day-to-daymaintenance tasks by…• *Easily* Versioning your database using Red Gate SQL SourceControl• Using Continuous Integration (via Jenkins) to validateDatabase builds• Using Jenkins to automate database deployments• Using CI / tSQLt / SQL Test to run unit tests
  5. 5. Prerequisites• Experience with source control management systems(svn, TFS, git, Hg)• Familiarity with Continuous Integration Products(Jenkins, Team City, Cruise Control)• Awareness of build scripting languages (ant,MSBuild)
  6. 6. What software is used?• SQL Server 2008 / 2012• Red Gate SQL Source Control• Red Gate SQL Compare• Red Gate SQL Data Compare• Jenkins Continuous Integration Serverhttp://jenkins-ci.org/– Promoted Build Plugin– Copy Artifacts Plugin– Version Plugin– Git Plugin• MSBuild
  7. 7. What is SQL Source Control?• Source Control Plug in for SQL Server ManagementStudio• Creates a “snapshot” of the database schema defined byCREATE scripts• Snapshot is consumable by SQL Compare and may beused to compare against the schema of an actualdatabase
  8. 8. What is SQL Source Control?SQL Source Control is to SSMSasTortoiseSVN is to Windows Explorer
  9. 9. Demo EnvironmentGitHubLocal Copy ofRGDemo databaseDev, QA, & ProdDatabasesDeveloper WorkstationBuild and Database Server(Windows Azure VM)
  10. 10. Committing Changes to SourceControlDemoLocal DatabaseChangesCommit Changesvia SQL SourceControlChanges committed toSCM repository
  11. 11. How does Continuous Integration fitin?• The CI server polls the repository for changes• When changes are checked in, the CI job kicks off– Verifies that the database can be built• Builds a brand new database from scratch using SQLCompare and SQL Data Compare– Runs unit tests• Build should fail if unit tests do not succeed– Archives the artifacts (for deployments)• Artifacts can include build/test reports– Emails engineers if there are problems
  12. 12. Breaking the BuildDemoCommit Changesvia SQL SourceControlCI Server Detects ChangesKicks off Build ProcessBuild can pass orfail validation
  13. 13. Deploying Changes to DifferentEnvironments• The Promoted Builds plug in can be used to deploychanges to Integration/QA/Staging/Productionenvironments• SQL Compare and SQL Data Compare are used todeploy changes between the sourced controlleddatabase and your development environments• Deploying to Production and/or Staging can beconfigured to just create the scripts as opposed toforcing the synchronization
  14. 14. Deploying to Dev / QADemoSQL Source ControlRepositorySQL Compare Development EnvironmentDatabase
  15. 15. Creating a Database “Version”• Make sure the Jenkins Versioning plugin is installed• Create a User Defined Function calleddbo.DATABASE_VERSION()• Create a build step that updates the UDF with theversion number• The updated UDF will be archived and used withdeployments
  16. 16. Versioning your DatabaseDemoCommit Changesvia SQL SourceControlCI Server DetectsChangesKicks off BuildProcessBuild Task updatesdbo.DATABASE_VERSION()FunctionUpdated UDFArchived
  17. 17. Unit Testing with tSQLt and SQL Test• tSQLt is an open source set of stored procedures andfunctions to facilitate Unit Testing in SQL databases• SQL Test is a wrapper around this framework thatintegrates with SSMS• Your build server can enforce that your unit tests passand generate reports
  18. 18. Unit Testing with tSQLt / SQL TestDemoCommit Changesvia SQL SourceControlCI Server DetectsChangesKicks off BuildProcessBuild Task executesUnit Test proceduresTests can pass orfail the build
  19. 19. What did SQL Source Control do for us?• Saves developers time (yay!)– No more maintaining update scripts– Don’t need to deploy scripts when QA needs changes• Identifies holes in your deployment process– Are developers making changes directly toproduction?– Are indexes/constraints missing from yourDev/QA/Prod environments?• Creates a definitive database build that can be easilydeployed and redeployed
  20. 20. Considerations• Environments must be pristine• Process must be changed and understood• Production change scripts should be scrutinized(especially for the first few releases)• Migration Scripts can be used to massage data• DB Replication requires more work for promotions
  21. 21. Appendix 1: Other CI Servers• Jenkins (open source)• Team City (JetBrains)• Bamboo (Atlassian)• CruiseControl / CruiseControl.NET (open source)
  22. 22. Appendix 2: Other Source ControlSystems• Subversion (SVN)• Git• Team Foundation Server• Mercurial (Hg)• AccuRev• Surround SCM
  23. 23. Links / Contact Info• ehwang@practicefusion.com• @ernestedcode• https://github.com/CF9/Databases.RGDemo• Practice Fusion is Hiring (email me)http://practicefusion.com/careers/• facebook.com/practicefusion• @practicefusion

×