Microsoft SQL Server MVP, Grant Fritchey, and Redgate's Arneh Eskandari, show how Redgate’s DLM (Database Lifecycle Management) solution works to improve your database development and deployment processes.
This webinar focuses on how to use new, improved migration scripts in SQL Source Control 5 to enable the automation of complex deployments without the risk of losing data. See how to:
- Version control your databases and share database changes with your team using SQL Source Control
- Build and test your database as part of a Continuous Integration Process using DLM Automation
- Automate your database deployment process with DLM Automation to ensure safe, reliable and repeatable deployments
- Monitor your database as it moves though the different environments with DLM Dashboard.
Grant and Arneh demo how the Redgate DLM tools plug into Git, TeamCity and Octopus Deploy.
5. Agenda
• Intro to Redgate
• The challenge of integrating databases into ALM
• The effects of poor database change management and
deployments
• Benefits of DLM and Continuous Delivery
• How can Redgate help?
• Demo
6. About Redgate
Over 600,000 technology professionals worldwide use Redgate tools, including
91% of fortune 100 companies.
Our philosophy is to design highly usable, reliable tools that solve problems
commonly faced by DBAs and developers.
7. The challenge of integrating
databases into ALM
• Business-critical data needs to be safely and correctly preserved
• Databases carry state that needs to be managed as part of rolling out
new or updating existing software
8. Poor Database Deployment Effects
• Databases are out of pace with application development
• Little or no traceability of database changes
• Inability to roll back to the previous version of a database
• Databases become a bottleneck in agile delivery processes
• Releases are less frequent and more risky
• Manual database processes prevent you from utilizing CI and
CD to their full extent
• Deployments require a lot of Dev and DBA hours
9. Benefits of DLM & Continuous Delivery
• Repeatability of processes, giving:
• Greater predictability over releases
• Efficiency by eliminating the repetition of a range of manual activities
• Faster speed of response to change through:
• The automated deployment of smaller units of change
• Greater reliability of the release process by:
• Providing a series of automated test stages prior to deployment
10. The Bottom Line
The 2016 State of DevOps report found that:
• IT performance strongly correlates with practices such as version control and
continuous delivery.
• High-performing IT organizations are more agile and reliable, deploying code 200
times more frequently with 3 times lower change failure rate.
• Firms with high-performing IT organizations are twice as likely to exceed their
profitability, market share, and productivity goals.
15. Need help?
Contact us: dlm@red-gate.com
DLM online resources: www.red-gate.com/products/dlm
DLM training & consultancy: http://www.red-gate.com/training/find-
a-consultant
Hinweis der Redaktion
Good Morning everybody, welcome to our webinar on database lifecycle management. This is one of our monthly webinars from the DLM series where each month we focus on the integration of our DLM 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 TFS as our source control system, Jenkins as our build system and Octopus Deploy as a release management tool.
We also have Grant Fritchey with us today. A lot of you already know Grant from the SQL Server community but I’ll let him introduce himself
My name is Arneh Eskandari and I’ve been with Redgate for just over 5 years. As a technical sales engineer I work with our customers on daily basis helping them setup a continuous delivery process for their SQL Server databases using our DLM solution. Here’s my contact information so please feel free to reach out if you’re interested in setting up a proof of concept with our tools or if you have any questions that we don’t get to address in our webinar today.
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.
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.
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.
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
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.
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
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
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