SQL Server is not an excuse to avoid DevOps
Working as a DevOps consultant in the field I hear this excuse all the time: "We can't do DevOps, we use a SQL database"
Handcrafted database deployments take days and are extremely fragile. This often leads DBAs to the misconception that introducing DevOps - which naturally leads to an increased cadence in deployments - will result in DBAs doing deployments all the time and with more breakages. We will dispel this misconception by showing how DevOps automation and a little discipline allow better testing, shorter release cycles, and reduced business risk. We will also discuss some techniques and best practices for introducing DevOps for SQL Server deployments.
Handcrafted database deployments take days and are extremely fragile. This often leads DBAs to the misconception that introducing DevOps - which naturally leads to an increased cadence in deployments - will result in DBAs doing deployments all the time and with more breakages. We will dispel this misconception by showing how DevOps automation and a little discipline allow better testing, shorter release cycles, and reduced business risk. We will also discuss some techniques and best practices for introducing DevOps for SQL Server deployments.
How did you like it?
We appreciate your privacy. Feedback is anonymous and is used to improve quality of our conferences.Other speaker sessions
Feature flags: the toggle, the A/B test and the canary
Session Detail
Will be announced