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
One thing I’ve always loved about the Scooby-Doo cartoon is that he never solved...
By Kevin3NF
Flexibility and Scale at the Database Level When SQL Server 2012 introduced Availability Groups...
Setting page visibility and the active page are often overlooked last steps when publishing...
Comments posted to this topic are about the item Password Guidance
Comments posted to this topic are about the item Using table variables in T-SQL
I am trying to check out elastic query between two test instances we have...
What happens if you run the following code in SQL Server 2022+?
declare @t1 table (id int); insert into @t1 (id) values (NULL), (1), (2), (3); select count(*) from @t1 where @t1.id is distinct from NULL;See possible answers