Have you ever longed for a way of making the delivery of databases more visible, predictable and measurable? Do you ever wish that they would be of better quality, quicker to change, and cost less? Grant Fritchey explains some of the secrets of doing Continuous Integration for Databases to relieve some of the pain-points of the Database Delivery process.
2020-11-18
In order to be able to deliver database changes more quickly, there are several tasks that must be automated. It can be a daunting job to ensure that the whole team has the latest database build when there is a proliferation of copies, and the database is big. Phil illustrates a solution by taking a set of Redgate tools to show how they can be used together, via PowerShell, to build a database from object-level source, stock it with data, document it, and then provision any number of test and development servers with the database build, taking care to save any DDL changes to the existing copies of the database.
2017-08-08
5,020 reads
The articles collected here will help you understand the theories and methodologies behind every stage of the database delivery pipeline, starting when database changes are checked in, and ending when they're deployed to production.
2014-06-12
4,888 reads
I was sick of changing context in Azure Data Studio while cleaning up things...
By Zikato
The crime spree in Digitown is not ending. This time 20 cars have been...
By Steve Jones
One of our mission statements in the Book of Redgate says: attempt to do...
Comments posted to this topic are about the item Shining a Light on Shadow...
Hi, I would love to hear if anyone can tell me why a CAST...
hi, one of our sister division's erp extract view is going thru at least...
In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?
See possible answers