< Back
Copy-DbaAgentSchedule
Post
NAME Copy-DbaAgentSchedule
SYNOPSIS
Copy-DbaAgentSchedule migrates shared job schedules from one SQL Server to another.
SYNTAX
Copy-DbaAgentSchedule [[-Source] <DbaInstanceParameter>] [[-SourceSqlCredential] <Pscredential>] [-Destination]
<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-DestinationSqlCredential] <Pscredential>]
[[-Schedule] <System.String[]>] [[-Id] <System.Int32[]>] [[-InputObject]
<Microsoft.SqlServer.Management.Smo.Agent.JobSchedule[]>] [-Force <Switch>] [-EnableException <Switch>]
[<CommonParameters>]
DESCRIPTION
All shared job schedules are copied.
If the associated credential for the account does not exist on the destination, it will be skipped. If the shared
job schedule 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
-Force [<Switch>]
If this switch is enabled, the Operator will be dropped and recreated on Destination.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Id [<System.Int32[]>]
Copy only specific schedule.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-InputObject [<Microsoft.SqlServer.Management.Smo.Agent.JobSchedule[]>]
Enables piping from Get-DbaAgentSchedule
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Schedule [<System.String[]>]
Copy only specific schedules. Note that SQL Server allows multiple schedules with the same name. Use Id for
more accurate schedule copies.
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, Agent
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-DbaAgentSchedule -Source sqlserver2014a -Destination sqlcluster
Copies all shared job schedules from sqlserver2014a to sqlcluster using Windows credentials. If shared job
schedules with the same name exist on sqlcluster, they will be skipped.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>Copy-DbaAgentSchedule -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force
Shows what would happen if the command were executed using force.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>Get-DbaAgentSchedule -SqlInstance sql2016 | Out-GridView -Passthru | Copy-DbaAgentSchedule -Destination
sqlcluster
Gets a list of schedule, outputs to a gridview which can be selected from, then copies to SqlInstance
RELATED LINKS
https://dbatools.io/Copy-DbaAgentSchedule
SYNOPSIS
Copy-DbaAgentSchedule migrates shared job schedules from one SQL Server to another.
SYNTAX
Copy-DbaAgentSchedule [[-Source] <DbaInstanceParameter>] [[-SourceSqlCredential] <Pscredential>] [-Destination]
<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-DestinationSqlCredential] <Pscredential>]
[[-Schedule] <System.String[]>] [[-Id] <System.Int32[]>] [[-InputObject]
<Microsoft.SqlServer.Management.Smo.Agent.JobSchedule[]>] [-Force <Switch>] [-EnableException <Switch>]
[<CommonParameters>]
DESCRIPTION
All shared job schedules are copied.
If the associated credential for the account does not exist on the destination, it will be skipped. If the shared
job schedule 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
-Force [<Switch>]
If this switch is enabled, the Operator will be dropped and recreated on Destination.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Id [<System.Int32[]>]
Copy only specific schedule.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-InputObject [<Microsoft.SqlServer.Management.Smo.Agent.JobSchedule[]>]
Enables piping from Get-DbaAgentSchedule
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Schedule [<System.String[]>]
Copy only specific schedules. Note that SQL Server allows multiple schedules with the same name. Use Id for
more accurate schedule copies.
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, Agent
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-DbaAgentSchedule -Source sqlserver2014a -Destination sqlcluster
Copies all shared job schedules from sqlserver2014a to sqlcluster using Windows credentials. If shared job
schedules with the same name exist on sqlcluster, they will be skipped.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>Copy-DbaAgentSchedule -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force
Shows what would happen if the command were executed using force.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>Get-DbaAgentSchedule -SqlInstance sql2016 | Out-GridView -Passthru | Copy-DbaAgentSchedule -Destination
sqlcluster
Gets a list of schedule, outputs to a gridview which can be selected from, then copies to SqlInstance
RELATED LINKS
https://dbatools.io/Copy-DbaAgentSchedule