Is the name of the publication. publication is sysname, with no default.

[ @publisher=] 'publisher'

Is the name of the Publisher. Publisher is sysname, with a default of the local server name. The Publisher must be a valid server.

[ @publisher_db =] 'publisher_db'

Is the name of the Publisher database. publisher_db is sysname, with a default of NULL.

[ @subscriber_type=] 'subscriber_type'

Is the type of Subscriber. subscriber_type is nvarchar(15), and can be global, local or anonymous. In SQL Server 2005, local subscriptions are referred to as client subscriptions and global subscriptions are referred to as server subscriptions. For more information, see the "Subscription Types" section in How Merge Replication Detects and Resolves Conflicts. A value of anonymous is required if you want to create a subscription without registering the subscription at the Publisher. This is necessary for cases such as Web synchronization, in which you cannot establish a SQL Server connection to the Publisher during subscription configuration.

[ @subscription_priority=] subscription_priority

Is the subscription priority. subscription_priorityis real, with a default of NULL. For local and anonymous subscriptions, the priority is 0.0. The priority is used by the default resolver to pick a winner when conflicts are detected. For global subscribers, the subscription priority must be less than 100, which is the priority of the publisher.

[ @sync_type=] 'sync_type'

Is the subscription synchronization type. sync_typeis nvarchar(15), with a default of automatic. Can be automatic or none. If automatic, the schema and initial data for published tables are transferred to the Subscriber first. If none, it is assumed the Subscriber already has the schema and initial data for published tables. System tables and data are always transferred.

Is a brief description of this pull subscription. descriptionis nvarchar(255), with a default of NULL. This value is displayed by the Replication Monitor in the Friendly Name column, which can be used to sort the subscriptions for a monitored publication.

If using SQL Server Agent to synchronize the subscription, the sp_addmergepullsubscription_agent stored procedure must be run at the Subscriber to create an agent and job to synchronize with the Publication.