A default profile for the Merge Agent is installed when a server is configured as a Distributor. The default profile contains the following parameters and values.
| Parameter | Default value | Description |
|---|---|---|
| -BcpBatchSize | 10000 | Is the number of rows to send a bulk copy operation. When performing a bcp in an operation while applying the schema changes, the Merge Agent uses the batch size to determine when to log a progress message. A value of 0 indicates no message logging. |
| -ChangesPerHistory | 50 | Is the threshold beyond which upload and download messages are logged. |
| -DownloadGenerationsPerBatch | 100 | Is the number of generations to be processed in a single batch while downloading changes from the Publisher to the Subscriber. A generation is defined as a logical group of changes per article. The default for an unreliable communication link is 10. |
| -DownloadReadChangesPerBatch | 100 | Is the number of changes to be read in a single batch while downloading changes from the Publisher to the Subscriber. |
| -DownloadWriteChangesPerBatch | 100 | Is the number of changes to be applied in a single batch while downloading changes from the Publisher to the Subscriber. |
| -FastRowCount | 1 | Specifies what type of rowcount calculation method should be used for rowcount validation. A value of 1 (default) indicates the fast method. A value of 0 indicates the full rowcount method. |
| -HistoryVerboseLevel | 1 | Specifies the amount of history logged during a merge operation. Can be:
1 = Always update a previous history message of the same status (startup, progress, success, and so forth). If no previous record with the same status exists, insert a new record. This level logs the minimum number of messages. 2 = Insert new history records unless the record is for such things as idle messages or long-running job messages, in which case update the previous records. This level logs level 1 messages plus additional in-progress messages. 3 = Always insert new records, unless it is for idle messages. You can minimize the performance effect of history logging by setting the ChangesPerHistory parameter. |
| -LoginTimeOut | 15 | Is the number of seconds before the login attempted by the agent times out. |
| -PollingInterval | 60 | Is how often, in seconds, the Publisher or Subscriber is queried for data changes when in continuous mode. |
| -QueryTimeOut | 300 | Is the number of seconds before the queries issued by the agent times out. |
| -UploadGenerationsPerBatch | 100 | Is the number of generations to be processed in a single batch while uploading changes from the Subscriber to the Publisher. A generation is defined as a logical group of changes per article. The default for an unreliable communication link is 1. |
| -UploadReadChangesPerBatch | 100 | Is the number of changes to be read in a single batch while uploading changes from the Subscriber to the Publisher. |
| -UploadWriteChangesPerBatch | 100 | Is the number of changes to be applied in a single batch while uploading changes from the Subscriber to the Publisher. |
| -Validate | 0 | Specifies if validation should be done at the end of the merge session, and, if so, what type of validation. A value of 0 (default) indicates no validation. A value of 1 indicates rowcount-only validation. A value of 2 indicates rowcount and checksum validation. |
| -ValidateInterval | 60 | Is how often, in minutes, the subscription is validated in continuous mode. |
| Replication Merge Agent Utility |