Red Gate forums: Deployment Manager PowerShell Scripts

RE: Include custom SQL script output in DM's deployment logs

chirayu — Tue, 04 Jun 2013 07:56:13 GMT

Glad it works! I have moved this topic to Powershell scripts forum.

Thanks!

Chirayu

RE: Include custom SQL script output in DM's deployment logs

swinghouse — Mon, 03 Jun 2013 22:04:09 GMT

Hi Chirayu,

Your suggestion worked beautifully!

After adding

Code:

| Out-Default

to the sqlmcd call, the script output is indeed captured by Deployment Manager.

Many thanks!

/Mattias

RE: Include custom SQL script output in DM's deployment logs

chirayu — Mon, 03 Jun 2013 13:03:41 GMT

Hi Mattias,

Deployment Manager should be capturing the std-out output from powershell scripts.

Windows powershell puts 'Out-Default' at the end of a pipeline, so what actually gets run is

Code:

sqlcmd.exe <arguments> | Out-Default

Out-Default cannot process some objects. It can only handle a special type of formatting object produced by the shell�s formatting subsystem, according to this article:
http://technet.microsoft.com/en-us/magazine/gg213852.aspx

Would you please run this command

Code:

sqlcmd.exe <arguments> | Out-Default

and check that it actually outputs something?

Thanks!

Chirayu

Include custom SQL script output in DM's deployment logs

swinghouse — Fri, 31 May 2013 14:57:37 GMT

In one of our Deployment Manager (DM) projects we let PostDeploy.ps1 run a customized SQL script like so:

Code:

sqlcmd.exe -b -V 1 -s $databaseServer -U $databaseUserName -P $databasePassword -i "RunMigrationScript.sql" -d "$databaseName"

This works, but it would be nice to have DM include the output (SQL Print statements in this case) from the SQL script file in the deployment log. Currently we get:

Quote:

2013-05-30 15:43:53 DEBUG Looking for PowerShell scripts named PostDeploy.ps1
2013-05-30 15:43:53 INFO Calling PowerShell script: 'C:\ProgramData\Red Gate\DeploymentAgent\Applications\Production.Data\BagheraDataMigration\0.116\PostDeploy.ps1'
2013-05-30 15:49:08 DEBUG Script 'C:\ProgramData\Red Gate\DeploymentAgent\Applications\Production.Data\BagheraDataMigration\0.116\PostDeploy.ps1' completed.
2013-05-30 15:49:08 DEBUG Script output:
2013-05-30 15:49:08 DEBUG
2013-05-30 15:49:08 DEBUG Return code of PowerShell script: 0

No script output in there!

Is it possible to get the script output in the DM deployment log? If so, what do we need to change?

/Mattias

PowerShell script for shutting down a running exe

swinghouse — Thu, 03 Jan 2013 10:02:58 GMT

This is probably basic stuff for many of you guys, but I got some really helpful assistance from the "Red Gaters" at http://www.red-gate.com/MessageBoard/viewtopic.php?p=59593#59593 when I needed to shut down an exe on the target machine before deploying an application to it.

Share your PowerShell deployment scripts

justin.caldicott — Fri, 14 Dec 2012 15:33:33 GMT

You can use this forum to share any PowerShell deployment scripts that you make, that you think will be useful to others.

Windows Services

justin.caldicott — Fri, 14 Dec 2012 14:57:19 GMT

This script uses the Service Control tool (sc.exe) to create or update a Windows Service. It assumes some variables have been set in the Deployment Manager web interface:

Code:

# These variables should be set via the Deployment Manager web interface:
#
# ServiceName - Name of the Windows service
# ServiceExecutable - Path to the .exe containing the service
#
# sc.exe is the Service Control utility in Windows
$service = Get-Service $ServiceName -ErrorAction SilentlyContinue
$fullPath = Resolve-Path $ServiceExecutable
if (! $service)
{
Write-Host "The service will be installed"
New-Service -Name $ServiceName -BinaryPathName $fullPath -StartupType Automatic
}
else
{
Write-Host "The service will be stopped and reconfigured"
Stop-Service $ServiceName -Force
& "sc.exe" config $service.Name binPath= $fullPath start= auto | Write-Host
}
Write-Host "Starting the service"
Start-Service $ServiceName

This script uses InstallUtil.exe to install custom Event Log sources and Windows Services:

Code:

$NetFrameworkDirectory = $([System.Runtime.InteropServices.RuntimeEnvironment]::GetRuntimeDirectory())
& (Join-Path $NetFrameworkDirectory "InstallUtil.exe") "path\to\my.dll" | Write-Host