Skip to content

Latest commit

 

History

History
76 lines (59 loc) · 3.49 KB

File metadata and controls

76 lines (59 loc) · 3.49 KB
title sp_dropmergepullsubscription (Transact-SQL) | Microsoft Docs
ms.custom
ms.date 03/03/2017
ms.prod sql-server-2016
ms.reviewer
ms.suite
ms.technology
replication
ms.tgt_pltfrm
ms.topic language-reference
applies_to
SQL Server
f1_keywords
sp_dropmergepullsubscription
sp_dropmergepullsubscription_TSQL
helpviewer_keywords
sp_dropmergepullsubscription
ms.assetid 9301dd80-72f7-4adb-9b13-87e7f9114248
caps.latest.revision 31
author BYHAM
ms.author rickbyh
manager jhubbard

sp_dropmergepullsubscription (Transact-SQL)

[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx_md]

Drops a merge pull subscription. This stored procedure is executed at the Subscriber on the subscription database.

Topic link icon Transact-SQL Syntax Conventions

Syntax

  
sp_dropmergepullsubscription [ @publication= ] 'publication'   
        , [ @publisher= ] 'publisher'   
        , [ @publisher_db= ] 'publisher_db'   
    [ , [ @reserved= ] 'reserved' ]  

Arguments

[ @publication=] 'publication'
Is the name of the publication. publication is sysname, with a default of NULL. This parameter is required. Specify a value of all to remove subscriptions to all publications

[ @publisher=] 'publisher'
Is the name of the Publisher. publisheris sysname, with a default of NULL. This parameter is required.

[ @publisher_db=] 'publisher_db'
Is the name of the Publisher database. publisher_dbis sysname, with a default of NULL. This parameter is required.

[ @reserved=] 'reserved'
Is reserved for future use. reserved is bit, with a default of 0.

Return Code Values

0 (success) or 1 (failure)

Remarks

sp_dropmergepullsubscription is used in merge replication.

sp_dropmergepullsubscription drops the Merge Agent for this merge pull subscription, although the Merge Agent is not created in sp_addmergepullsubscription.

Example

[!code-sqlHowTo#sp_dropmergepullsubscription]

Permissions

Only members of the sysadmin fixed server role or the user that created the merge pull subscription can execute sp_dropmergepullsubscription. The db_owner fixed database role is only able to execute sp_dropmergepullsubscription if the user that created the merge pull subscription belongs to this role.

See Also

Delete a Pull Subscription
sp_addmergepullsubscription (Transact-SQL)
sp_changemergepullsubscription (Transact-SQL)
sp_dropmergesubscription (Transact-SQL)
sp_helpmergepullsubscription (Transact-SQL)