When the different teams that are involved throughout the life of a database fail to reconcile their different roles and priorities, and so fail to cooperate or work adaptively, the result is gridlock: databases defined as though carved in stone rather than by code and data. William Brewer explores how DLM can offer an alternative that allows databases to respond quickly to business change.
2015-08-13
7,221 reads
Redgate’s Database Lifecycle Management solution ensures database changes made in development environments are always tested and reviewed before being deployed, and adds automation to the process. Find out how by joining Steve Jones, MVP and editor of SQLServerCentral, as he demonstrates the solution and shows why such an approach is essential if you want to release changes frequently.
2015-09-22 (first published: 2015-08-11)
8,420 reads
PASS attendees will get the chance to learn about Database Lifecycle Management (DLM) straight from its chief proponent: Red Gate Software, the database and .NET tooling company.
2014-11-03
184 reads
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers