Extending DevOps practices to SQL Server databases - story tracking - 20th june 17

Editor's Notes

• #3: Good Morning everybody, welcome to our webinar on database DevOps. This is one of our monthly webinars series where each month we focus on the integration of our automation tools with different source control systems as well as build and release management tools. Our demo last month was on the integration with the TFS stack so using TFS to source control, build and deploy database changes. Today, we are going to change things up a little and use Git as our source control system, Jenkins as our build system and Octopus Deploy as a release management tool.
• #6: We’re going to run through a couple of slides to quickly go over the challenges with database change management and we’ll jump right into the demo afterwards. Just a couple of housekeeping items, everyone will be on mute throughout the webinar but please do post your questions using the gotowebinar panel and we’ll try to answer as many of them as possible towards the end of our session today.
• #7: Most of you are familiar with Redgate and have probably used our tools to some extent. I’d actually like to run a quick poll to see how familiar everyone is with Redgate tools For those of you who are new to Redgate, we are a software company and have been specializing in SQL Server tools specifically for developers and DBAs for just over 16 years now. We are also pretty big on supporting the community. So, we have our SQL Server Central and Simple Talk websites were you can find thousands of free articles and training material on SQL server. We also do sponsor a lot of free community events such as SQL Saturdays and code camps.
• #8: Alright, now let’s talk about the challenges with database change management. A lot of dev shops out there are already utilizing best practices around application lifecycle management and rapid delivery of their application code but the databases are normally left out and there are still a lot of manual processes involved in delivering database changes. This is mainly because deployments of databases is not as easy as swapping out old code with a new one. Databases carry state and hold business critical data that needs to be safely preserved.
• #9: Because of the unique challenges with database delivery, we’ve come across a lot of dev shops who’ve experienced some of the issues in this list to some extent. As Part of our database delivery process we need to make sure that we are executing the right changes on our target databases going all the way production and we also need to make sure that we have changes from all developers in the right order so, without the right tooling and the right processes this can become a cumbersome task for developers and specifically for operation DBAs
• #10: Most of you are probably familiar with the principles of Application Lifecycle Management and DLM here is no different. Our focus is to help build repeatability into your delivery process where you are continuously testing the production readiness of the changes that you apply to your databases. Deploying small units of change is really the key principal here. I’ve talked to a lot of dbas who are required to review thousands of lines of scripts when it comes to deploying the database and that normally can take days depending on how many bugs they find in that script. By committing database changes to source control on regular basis, you can introduce automated builds and tests to make sure that all of those small units of changes are tested and validated multiple times before you are ready to deploy from dev to your next environment and that can result into your releases being more reliable and less time consuming.
• #11: This statement from DevOps report is pretty relevant here. IT shops who utilize best practices around continuous delivery, deploy code more frequently and with more confidence. And that enables them to be more agile in their software delivery process and makes the company twice as likely to exceed their profitability
• #12: This statement from DevOps report is pretty relevant here. IT shops who utilize best practices around continuous delivery, deploy code more frequently and with more confidence. And that enables them to be more agile in their software delivery process and makes the company twice as likely to exceed their profitability
• #13: This statement from DevOps report is pretty relevant here. IT shops who utilize best practices around continuous delivery, deploy code more frequently and with more confidence. And that enables them to be more agile in their software delivery process and makes the company twice as likely to exceed their profitability
• #14: This statement from DevOps report is pretty relevant here. IT shops who utilize best practices around continuous delivery, deploy code more frequently and with more confidence. And that enables them to be more agile in their software delivery process and makes the company twice as likely to exceed their profitability