So often, the unexpected delays in delivering database code are more likely to happen after the developers initiate the release process. The necessary checks and tests can turn up surprises: The handover process can expose deficiencies. With good teamwork, planning and forethought, though, the process can be made almost painless.
2016-08-05
4,063 reads
A script I can run after deployment to refresh views and force a recompile due to modified DDL.
2016-03-18 (first published: 2016-03-03)
590 reads
The frequency of releasing software varies widely in the industry. If the test and release process is made as reliable and predictable as possible, then everyone gains. But how do you get started?
2014-02-03
2,729 reads
Databases often need more than just the database objects to run. There may be certain server objects and components, and SQL Agent objects, that are required as well. For an automated deployment, these need to be identified and their build script placed in source control. They then need to be deployed via the pre, or post deployment script. Phil spells out how and why.
2013-05-29
2,424 reads
Alex talks through a simple practical example of a database deployment, First creating a empty database and then upgrading it through three steps by writing T-SQL scripts, adjusting configuration files and the change log, before generating a full build script containing all schema objects.
2013-04-09
3,749 reads
There are a number of challenges that make the deployment task more difficult. Alex reviews the common techniques for deploying new databases and upgrading existing ones, and their flaws, and argues the advantages of an automated, incremental, script-based approach to deployments.
2013-03-18
3,067 reads
Although databases have no inherent way of recording their version numbers, SQL Server provides the means of doing so, and much more besides. This is a great advantage to anyone faced with the task of deploying databases without errors.
2013-03-11
2,601 reads
Often, an existing database application must evolve rapidly by incremental steps. Alex describes a tried and tested system to provide an automated approach to deploying both new and existing database systems, whilst dealing with common security and configuration issues.
2013-03-05
3,607 reads
When you are about to deploy a new version of a database by updating the current version, one of the essential pre-deployment checks is to make sure that the version in production is exactly what it should be. If changes have somehow slipped in, you'll need to understand them and deal with them before you can deploy.
2012-12-27
2,774 reads
As part of Simple-Talk's long-running Cribsheet series, they asked William Brewer to write a guide to deployment that described in general terms what is involved in the deployment of a database application, and the sort of issues you're likely to come up against.
2012-12-14
2,216 reads
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
By Steve Jones
One of the things that I like about the SQL Server docs (MS Learn...
I have change tracking configured in several databases, in QA and production environments, and...
is there a no code way to limit an ssis extract from excel to...
Hello Need help in pivoting this data set, the Pivot takes MIN/MAX on a...
In SQL Server 2025, what does this return?
CREATE TABLE Numbers ( n INT) GO INSERT dbo.Numbers ( n ) VALUES (1), (2), (3) GO SELECT PRODUCT(n) FROM dbo.NumbersSee possible answers