New-DlmDatabaseConnection

Creates an object that other DLM Automation cmdlets can use to connect to a database.

Syntax

Description

The New-DlmDatabaseConnection cmdlet creates a DatabaseConnection object that can be used by other DLM Automation cmdlets to connect to a database. The object contains the server instance, database name, and security credentials that cmdlets will use to connect to the database.

You can use Windows authentication or SQL Server authentication to connect to the database. If you use the Username and Password parameters, SQL Server authentication will be used. If you don't use those parameters, Windows authentication will be used; the account used to connect will be the account running PowerShell or the PowerShell script.

The cmdlets that can use the Database Connection object to connect to a database are Invoke-DlmDatabaseSchemaValidation, New-DlmDatabaseRelease, Sync-DlmDatabaseSchema, Test-DlmDatabaseConnection and Use-DlmDatabaseRelease.

As an alternative to using this cmdlet, you may use a standard database connection string in place of a Database Connection object. The following connection string properties are supported: ApplicationIntent, Asynchronous Processing, AttachDbFilename, Connect Timeout, Context Connection, Current Language, Data Source, Encrypt, Enlist, Failover Partner, Initial Catalog, Integrated Security, Load Balance Timeout, Max Pool Size, Min Pool Size, MultipleActiveResultSets, MultiSubnetFailover, Network Library, Packet Size, Password, Persist Security Info, Replication, Transaction Binding, TrustServerCertificate, Type System Version, User ID, User Instance and Workstation ID.

Parameters

-ServerInstance <System.String>

The name or network address of the SQL Server instance to connect to. For example, "rg-staging01\SQL2014". This is equivalent to the Data Source property of a connection string.

-Database <System.String>

The database to connect to, on the server specified in ServerInstance. This is equivalent to the Initial Catalog property of a connection string.

-Username <System.String>

The username for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the User ID property of a connection string. This parameter is optional. If you specify a null or empty string, Windows Authentication will be used and the Password parameter will be ignored.

-Password <System.String>

The password for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the Password property of a connection string. This parameter is optional. If left unspecified, it defaults to the empty string.

This parameter is ignored if the Username parameter is null or empty.

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see http://technet.microsoft.com/en-us/library/hh847884.aspx.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

• None.
  You cannot pipe input to this cmdlet.

Return values

The output type is the type of the objects that the cmdlet emits.

• RedGate.DLMAutomation.Compare.SchemaSources.DatabaseConnection

Examples

---------- EXAMPLE 1 ----------

$staging = New-DlmDatabaseConnection -ServerInstance "rg-staging01\SQL2014" -Database "AdventureWorks" -Username "sa" -Password "P@ssw0rd"

This example shows how to create a Database Connection object. The object will use SQL Server authentication to connect to the database.

The New-DlmDatabaseConnection cmdlet creates a Database Connection object, $staging. This can be used to connect to the database, AdventureWorks, on the SQL Server rg-staging01\SQL2014. Because the Username and Password parameters are provided, SQL Server authentication will be used to connect to AdventureWorks.

---------- EXAMPLE 2 ----------

$staging = New-DlmDatabaseConnection -ServerInstance "rg-staging01\SQL2014" -Database "AdventureWorks"

This example shows how to create a Database Connection object that will use Windows authentication to connect to the database.

The New-DlmDatabaseConnection cmdlet creates a Database Connection object, $staging. This can be used to connect to the database AdventureWorks on the SQL Server rg-staging01\SQL2014. Because no Username and Password are provided, Windows authentication will be used to connect to the database.

---------- EXAMPLE 3 ----------

$staging = New-DlmDatabaseConnection -ServerInstance "rg-staging01\SQL2014" -Database "Staging"
$test = New-DlmDatabaseConnection -ServerInstance "rg-test01\SQL2014" -Database "Test"
New-DlmDatabaseRelease -Source $test -Target $staging

This example shows how Database Connection objects can be used by the New-DlmDatabaseRelease cmdlet to create a Database Release.

The New-DlmDatabaseConnection cmdlet creates two Database Connection objects, $staging and $test. $staging is used to connect to the database, Staging, on rg-staging01\SQL2014. $test is used to connect to the database, Test, on rg-test01\SQL2014.

The New-DlmDatabaseRelease cmdlet creates the database deployment resources that can be used to update Staging to match the Test schema.

---------- EXAMPLE 4 ----------

$staging = New-DlmDatabaseConnection -ServerInstance "rg-staging01\SQL2014" -Database "Staging" | Test-DlmDatabaseConnection

This example shows how to create a Database Connection object and pass it through the pipeline to another cmdlet.

The New-DlmDatabaseConnection cmdlet creates a Database Connection object. It's piped through the Test-DlmDatabaseConnection cmdlet, before being assigned to $staging.

The Test-DlmDatabaseConnection cmdlet checks the Staging database can be connected to with the settings specified. This allows you to check you can connect to the Staging database before you use $staging with other cmdlets.