< Back

Copy-DbaStartupProcedure

Mon Jan 13, 2020 9:41 am

NAME Copy-DbaStartupProcedure



SYNOPSIS

Copy-DbaStartupProcedure migrates startup procedures (user defined procedures within master database) from one SQL

Server to another.





SYNTAX

Copy-DbaStartupProcedure [-Source] <DbaInstanceParameter> [[-SourceSqlCredential] <Pscredential>] [-Destination]

<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-DestinationSqlCredential] <Pscredential>]

[[-Procedure] <System.String[]>] [[-ExcludeProcedure] <System.String[]>] [-Force <Switch>] [-EnableException

<Switch>] [<CommonParameters>]





DESCRIPTION

By default, all procedures found flagged as startup procedures are copied and then set as a startup procedure on

the destination instance. The -Procedure parameter is auto-populated for command-line completion and can be used

to copy only specific startup procedures.



If the procedure already exists on the destination, it will be skipped unless -Force is used.





PARAMETERS

-Destination [<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]>]

Destination SQL Server. You must have sysadmin access and the server must be SQL Server 2000 or higher.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-DestinationSqlCredential [<Pscredential>]

Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).



Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory -

Integrated are all supported.



For MFA support, please use Connect-DbaInstance.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-EnableException [<Switch>]

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.

This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables

advanced scripting.

Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own

try/catch.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-ExcludeProcedure [<System.String[]>]

The startup procedure(s) to exclude. This list is auto-populated from the server.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-Force [<Switch>]

If this switch is enabled, the custom error will be dropped and recreated if it already exists on Destination.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-Procedure [<System.String[]>]

The startup procedure(s) to process. This list is auto-populated from the server. If unspecified, all startup

procedures will be processed.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-Source [<DbaInstanceParameter>]

Source SQL Server. You must have sysadmin access and server version must be SQL Server version 2000 or higher.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



-SourceSqlCredential [<Pscredential>]

Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).



Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory -

Integrated are all supported.



For MFA support, please use Connect-DbaInstance.



Required? false

Position? named

Default value

Accept pipeline input? False

Accept wildcard characters? false



<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).



INPUTS



OUTPUTS



NOTES





Tags: Migration, Procedure, Startup, StartupProcedure

Author: Shawn Melton (@wsmelton), http://wsmelton.github.io



Website: https://dbatools.io

Copyright: (c) 2018 by dbatools, licensed under MIT

License: MIT https://opensource.org/licenses/MIT



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



PS C:\\>Copy-DbaStartupProcedure -Source sqlserver2014a -Destination sqlcluster



Copies all startup procedures from sqlserver2014a to sqlcluster using Windows credentials. If procedure(s) with

the same name exists in the master database on sqlcluster, they will be skipped.

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



PS C:\\>Copy-DbaStartupProcedure -Source sqlserver2014a -SourceSqlCredential $scred -Destination sqlcluster

-DestinationSqlCredential $dcred -Procedure logstartup -Force



Copies only the startup procedure, logstartup, from sqlserver2014a to sqlcluster using SQL credentials for

sqlserver2014a and Windows credentials for sqlcluster. If the procedure already exists on sqlcluster, it will be

updated because -Force was used.

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



PS C:\\>Copy-DbaStartupProcedure -Source sqlserver2014a -Destination sqlcluster -ExcludeProcedure logstartup -Force



Copies all the startup procedures found on sqlserver2014a except logstartup to sqlcluster. If a startup procedure

with the same name exists on sqlcluster, it will be updated because -Force was used.

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



PS C:\\>Copy-DbaStartupProcedure -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force



Shows what would happen if the command were executed using force.



RELATED LINKS

https://dbatools.io/Copy-DbaStartupProcedure