| title | Initialize Subscriptions | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/14/2017 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | replication | |
| ms.topic | conceptual | |
| f1_keywords |
|
|
| ms.assetid | 7b170e4e-470d-4828-a9ed-7435b0b03514 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| monikerRange | =azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allversions |
[!INCLUDEappliesto-ss-asdbmi-xxxx-xxx-md] Subscribers must be initialized before they can begin receiving replicated data. An initial dataset is not required, but the Subscriber must at least have the schema for each replicated object and any metadata tables and procedures required by replication.
Subscription properties
Select the check box in the Initialize column for each Subscriber that requires an initial data set. If the check box is cleared, only the replication metadata and procedures will be initialized. For more information about initializing a subscription without a snapshot, see Initialize a Transactional Subscription Without a Snapshot.
Select Immediately from the drop-down list box in the Initialize When column to have the Merge Agent or Distribution Agent transfer snapshot files to the Subscriber after this wizard is completed. Select At first synchronization to have the agent transfer the files the next time it is scheduled to run. The Immediately option is not available for pull subscriptions to [!INCLUDEmsCoName] [!INCLUDEssExpress]. The Merge Agent and Distribution Agent do not run on instances of [!INCLUDEssExpress]; therefore the subscription must be initialized through another method.
Note
The wizard might prompt for a connection to the Distributor in order to start the appropriate job for the Distribution Agent or Merge Agent.
Create a Pull Subscription
Create a Push Subscription
Initialize a Subscription
Subscribe to Publications