Events
Apr 8, 3 PM - May 28, 7 AM
Sharpen your AI skills and enter the sweepstakes to win a free Certification exam
Register now!This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to:
SQL Server
Azure SQL Managed Instance
Changes the Distribution Agent or Merge Agent schedule for a subscriber. This stored procedure is executed at the Publisher on any database.
Transact-SQL syntax conventions
sp_changesubscriber_schedule
[ @subscriber = ] N'subscriber'
, [ @agent_type = ] agent_type
[ , [ @frequency_type = ] frequency_type ]
[ , [ @frequency_interval = ] frequency_interval ]
[ , [ @frequency_relative_interval = ] frequency_relative_interval ]
[ , [ @frequency_recurrence_factor = ] frequency_recurrence_factor ]
[ , [ @frequency_subday = ] frequency_subday ]
[ , [ @frequency_subday_interval = ] frequency_subday_interval ]
[ , [ @active_start_time_of_day = ] active_start_time_of_day ]
[ , [ @active_end_time_of_day = ] active_end_time_of_day ]
[ , [ @active_start_date = ] active_start_date ]
[ , [ @active_end_date = ] active_end_date ]
[ , [ @publisher = ] N'publisher' ]
[ ; ]
The name of the Subscriber. @subscriber is sysname, with no default. The name of the Subscriber must be unique in the database, must not already exist, and can't be NULL
.
The type of agent. @agent_type is smallint, with a default of 0
.
0
indicates a Distribution Agent.1
indicates a Merge Agent.Specifies the frequency with which to schedule the distribution task. @frequency_type is int, and can be one of these values.
Value | Description |
---|---|
1 |
One time |
2 |
On demand |
4 |
Daily |
8 |
Weekly |
16 |
Monthly |
32 |
Monthly relative |
64 (default) |
Autostart |
128 |
Recurring |
The value applied to the frequency set by @frequency_type. @frequency_interval is int, and depends on the value of @frequency_type.
Value of @frequency_type | Effect on @frequency_interval |
---|---|
1 (default) |
@frequency_interval is unused. |
4 |
Every @frequency_interval days. |
8 |
@frequency_interval is one or more of the following (combined with a | (Bitwise OR) logical operator):1 = Sunday2 = Monday4 = Tuesday8 = Wednesday16 = Thursday32 = Friday64 = Saturday |
16 |
On the @frequency_interval day of the month. |
32 |
@frequency_interval is one of the following options:1 = Sunday2 = Monday3 = Tuesday4 = Wednesday5 = Thursday6 = Friday7 = Saturday8 = Day9 = Weekday10 = Weekend day |
64 |
@frequency_interval is unused. |
128 |
@frequency_interval is unused. |
The date of the distribution task. @frequency_relative_interval is int, and can be one of these values.
Value | Description |
---|---|
1 (default) |
First |
2 |
Second |
4 |
Third |
8 |
Fourth |
16 |
Last |
The recurrence factor used by @frequency_type. @frequency_recurrence_factor is int, with a default of 0
.
Specifies how often, in minutes, to reschedule during the defined period. @frequency_subday is int, and can be one of these values.
Value | Description |
---|---|
1 |
Once |
2 |
Second |
4 (default) |
Minute |
8 |
Hour |
The number of frequency_subday periods that occur between each execution of the job. @frequency_subday_interval is int, with a default of 5
.
The time of day when the distribution task is first scheduled. @active_start_time_of_day is int, with a default of NULL
.
The time of day when the distribution task stops being scheduled. @active_end_time_of_day is int, with a default of 235959
, which means 11:59:59 P.M. on a 24-hour clock.
The date when the distribution task is first scheduled, formatted as yyyyMMdd
. @active_start_date is int, with a default of NULL
.
The date when the distribution task stops being scheduled, formatted as yyyyMMdd
. @active_end_date is int, with a default of 99991231
, which means December 31, 9999.
Specifies a non-SQL Server Publisher. @publisher is sysname, with a default of NULL
.
@publisher shouldn't be used when changing article properties on a SQL Server Publisher.
0
(success) or 1
(failure).
sp_changesubscriber_schedule
is used in all types of replication.
Only members of the sysadmin fixed server role can execute sp_changesubscriber_schedule
.
Events
Apr 8, 3 PM - May 28, 7 AM
Sharpen your AI skills and enter the sweepstakes to win a free Certification exam
Register now!