Applies To: SQL Server 2014, SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Changes selected properties of a merge push subscription. This stored procedure is executed at the Publisher on the publication database.
sp_changemergesubscription [ [ @publication= ] 'publication' ]
[ , [ @subscriber= ] 'subscriber'
[ , [ @subscriber_db= ] 'subscriber_db' ]
[ , [ @property= ] 'property' ]
[ , [ @value= ] 'value' ]
@publication=] ' publication '
Is the name of the publication to change.
publication is sysname, with a default of NULL. The publication must already exist and must conform to the rules for identifiers.
@subscriber=] ' subscriber '
Is the name of the Subscriber.
subscriber is sysname, with a default of NULL.
@subscriber_db=] ' subscriber_db '
Is the name of the subscription database.
subscriber_dbis sysname, with a default of NULL.
@property=] ' property '
Is the property to change for the given publication.
property is sysname, and can be one of the values in the table.
@value=] ' value '
Is the new value for the specified
property. value is nvarchar(255), and can be one of the values in the table.
Description of this merge subscription.
Is the subscription priority. The priority is used by the default resolver to pick a winner when conflicts are detected.
Login for the Microsoft Windows account under which the agent runs.
Password for the Windows account under which the agent runs.
Use Windows Authentication when connecting to the Publisher.
Use SQL Server Authentication when connecting to the Publisher.
Login name at the Publisher.
Strong password for the supplied Publisher login.
Use Windows Authentication when connecting to the Subscriber.
Use SQL Server Authentication when connecting to the Subscriber.
Login name at the Subscriber.
Strong password for the supplied Subscriber login.
Schema and initial data for published tables are transferred to the Subscriber first.
Subscriber already has the schema and initial data for published tables; system tables and data are always transferred.
Allows conflicts to be resolved interactively for all articles that allow interactive resolution.
Conflicts are resolved automatically using a default resolver or custom resolver.
0 (success) or 1 (failure)
sp_changemergesubscription is used in merge replication.
After changing an agent login or password, you must stop and restart the agent before the change takes effect.
Only members of the
sysadmin fixed server role or db_owner fixed database role can execute sp_changemergesubscription.