< Back
Copy-DbaInstanceTrigger
Post
NAME Copy-DbaInstanceTrigger
SYNOPSIS
Copy-DbaInstanceTrigger migrates server triggers from one SQL Server to another.
SYNTAX
Copy-DbaInstanceTrigger [-Source] <DbaInstanceParameter> [[-SourceSqlCredential] <Pscredential>] [-Destination]
<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-DestinationSqlCredential] <Pscredential>]
[[-ServerTrigger] <System.Object[]>] [[-ExcludeServerTrigger] <System.Object[]>] [-Force <Switch>]
[-EnableException <Switch>] [<CommonParameters>]
DESCRIPTION
By default, all triggers are copied. The -ServerTrigger parameter is auto-populated for command-line completion
and can be used to copy only specific triggers.
If the trigger 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 server version must be SQL Server version 2000 or
greater.
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
-ExcludeServerTrigger [<System.Object[]>]
The Server Trigger(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>]
Drops and recreates the Trigger if it exists
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-ServerTrigger [<System.Object[]>]
The Server Trigger(s) to process - this list is auto-populated from the server. If unspecified, all Server
Triggers 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 greater.
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
Author: Chrissy LeMaire (@cl), netnerds.net
Website: https://dbatools.io
Copyright: (c) 2018 by dbatools, licensed under MIT
License: MIT https://opensource.org/licenses/MIT
Requires: sysadmin access on SQL Servers
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster
Copies all server triggers from sqlserver2014a to sqlcluster, using Windows credentials. If triggers with the same
name exist on sqlcluster, they will be skipped.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster -ServerTrigger tg_noDbDrop
-SourceSqlCredential $cred -Force
Copies a single trigger, the tg_noDbDrop trigger from sqlserver2014a to sqlcluster, using SQL credentials for
sqlserver2014a and Windows credentials for sqlcluster. If a trigger with the same name exists on sqlcluster, it
will be dropped and recreated because -Force was used.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force
Shows what would happen if the command were executed using force.
RELATED LINKS
https://dbatools.io/Copy-DbaInstanceTrigger
SYNOPSIS
Copy-DbaInstanceTrigger migrates server triggers from one SQL Server to another.
SYNTAX
Copy-DbaInstanceTrigger [-Source] <DbaInstanceParameter> [[-SourceSqlCredential] <Pscredential>] [-Destination]
<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-DestinationSqlCredential] <Pscredential>]
[[-ServerTrigger] <System.Object[]>] [[-ExcludeServerTrigger] <System.Object[]>] [-Force <Switch>]
[-EnableException <Switch>] [<CommonParameters>]
DESCRIPTION
By default, all triggers are copied. The -ServerTrigger parameter is auto-populated for command-line completion
and can be used to copy only specific triggers.
If the trigger 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 server version must be SQL Server version 2000 or
greater.
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
-ExcludeServerTrigger [<System.Object[]>]
The Server Trigger(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>]
Drops and recreates the Trigger if it exists
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-ServerTrigger [<System.Object[]>]
The Server Trigger(s) to process - this list is auto-populated from the server. If unspecified, all Server
Triggers 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 greater.
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
Author: Chrissy LeMaire (@cl), netnerds.net
Website: https://dbatools.io
Copyright: (c) 2018 by dbatools, licensed under MIT
License: MIT https://opensource.org/licenses/MIT
Requires: sysadmin access on SQL Servers
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster
Copies all server triggers from sqlserver2014a to sqlcluster, using Windows credentials. If triggers with the same
name exist on sqlcluster, they will be skipped.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster -ServerTrigger tg_noDbDrop
-SourceSqlCredential $cred -Force
Copies a single trigger, the tg_noDbDrop trigger from sqlserver2014a to sqlcluster, using SQL credentials for
sqlserver2014a and Windows credentials for sqlcluster. If a trigger with the same name exists on sqlcluster, it
will be dropped and recreated because -Force was used.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>Copy-DbaInstanceTrigger -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force
Shows what would happen if the command were executed using force.
RELATED LINKS
https://dbatools.io/Copy-DbaInstanceTrigger