Date: Thu, 28 Mar 2024 20:15:34 +0000 (GMT) Message-ID: <430842268.489.1711656934987@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_488_1839323067.1711656934980" ------=_Part_488_1839323067.1711656934980 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can deploy SQL Server databases with Deployment Manager usin= g database packages.
This article describes:
Applications
For information about creating application packages, see Packaging applications.
Database packages contain database object creation scripts representing = the state of a database (including any static data). Packages can also cont= ain:
Deployment Manager upgrades databases in one of two ways:
Deployment Manager can validate a deployment by checking that the state = of the database you are deploying to is identical to the state of the datab= ase in the package.
There are two types of validation:
When you deploy a database with Deployment Manager, or when you package = a database using the SSMS add-in, the table-valued function Deploym= entManagerLastDeployment() is added to the database. It = has two columns, each with one row:
When deploying a database with Deployment Manager, the properties are se= t with the package name and version of the package that you're deploying. W= hen packaging databases using the SSMS add-in, the properties are set to th= e most recent package name and version you published.
The function is added to the RedGateLocal schema.
When you first deploy a database with Deployment Manager, two extended p= roperties are added to the database:
Deployment Manager uses these extended properties in future pre-deployme= nt validations and static upgrades.
In future pre-deployment validations, the extended properties will be us= ed to ensure that the database is validated against the correct package ver= sion.
In future static upgrades, the extended properties will be used to ensur= e that the correct upgrade script is used during the deployment.
The extended properties are updated automatically with each deployment.<= /p>
Before Deployment Manager 2.2.6, you cannot deploy SQL Azure databases w= ith Deployment Manager because SQL Azure does not support extended properti= es.
You can create and publish database packages from SQL Server Manage= ment Studio (SSMS) using the Deployment Manager add-in. For informatio= n, see:
If you're using TeamCity as your continuous integration server= , see:
If you aren't using TeamCity, you can automate the creation of database = packages with MSBuild:
To deploy database packages with Deployment Manager, you need to specify= some variables in your project. For details, see: