Prints all available parameters.
Is the name of the Publisher. Specify server_name for the default instance of SQL Server on that server. Specify server_name\instance_name for a named instance of SQL Server on that server.
Is the name of the Publisher database.
Is the name of the Subscriber. Specify server_name for the default instance of SQL Server on that server. Specify server_name\instance_name for a named instance of SQL Server on that server.
Is the name of the Subscriber database.
Is the path to the folder that contains the initial snapshot for a subscription.
Is the number of rows to send in a bulk copy operation. When performing a bcp in operation, the batch size is the number of rows to send to the server as one transaction, and also the number of rows that must be sent before the Distribution Agent logs a bcp progress message. When performing a bcp out operation, a fixed batch size of 1000 is used.
Is the number of transactions to be issued to the Subscriber before a COMMIT statement is issued. The default is 100.
- -CommitBatchThreshold commit_batch_threshold
Is the number of replication commands to be issued to the Subscriber before a COMMIT statement is issued. The default is 1000.
Specifies whether the agent attempts to poll replicated transactions continually. If specified, the agent polls replicated transactions from the source at polling intervals, even if there are no transactions pending.
-Continuous should not be specified with -MaxDeliveredTransactions. For more information, see -MaxDeliveredTransactions entry later in this topic.
Is the path of the agent definition file. An agent definition file contains command prompt arguments for the agent. The content of the file is parsed as an executable file. Use double quotation marks (") to specify argument values containing arbitrary characters.
Is the Distributor name. For Distributor (push) distribution, the name defaults to the name of the local Distributor.
Is the Distributor login name.
Is the Distributor password.
- -DistributorSecurityMode[ 0| 1]
Specifies the security mode of the Distributor. A value of 0 indicates SQL Server Authentication Mode, and a value of 1 indicates Windows Authentication Mode (default).
- -EncryptionLevel [ 0 | 1 | 2 ]
Is the level of Secure Sockets Layer (SSL) encryption used by the Distribution Agent when making connections.
Specifies that SSL is not used.
Specifies that SSL is used, but the agent does not verify that the SSL server certificate is signed by a trusted issuer.
Specifies that SSL is used, and that the certificate is verified.
For more information, see Security Overview (Replication).
Is the path and file name of the error file generated by the Distribution Agent. This file is generated at any point where failure occurred while applying replication transactions at the Subscriber; errors that occur at the Publisher or Distributor are not logged in this file. This file contains the failed replication transactions and associated error messages. When not specified, the error file is generated in the current directory of the Distribution Agent. The error file name is the name of the Distribution Agent with an .err extension. If the specified file name exists, error messages are appended to the file. This parameter can be a maximum of 256 Unicode characters.
- -FileTransferType [ 0| 1]
Specifies the file transfer type. A value of 0 indicates UNC (universal naming convention), and a value of 1 indicates FTP (file transfer protocol).
Is the network address of the FTP service for the Distributor. When not specified, DistributorAddress is used. If DistributorAddress is not specified, Distributor is used.
Is the user password used to connect to the FTP service.
Is the port number of the FTP service for the Distributor. When not specified, the default port number for FTP service (21) is used.
- -FtpUserName ftp_user_name
Is the user name used to connect to the FTP service. When not specified, anonymous is used.
- -HistoryVerboseLevel[ 0 | 1 | 2 | 3 ]
Specifies the amount of history logged during a distribution operation. You can minimize the performance effect of history logging by selecting 1.
Progress messages are written either to the console or to an output file. History records are not logged in the distribution database.
Default. Always update a previous history message of the same status (startup, progress, success, and so on). If no previous record with the same status exists, insert a new record.
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.
Always insert new records, unless it is for idle messages.
Is the host name used when connecting to the Publisher. This parameter can be a maximum of 128 Unicode characters.
Is the number of seconds before the history thread checks if any of the existing connections is waiting for a response from the server. This value can be decreased to avoid having the checkup agent mark the Distribution Agent as suspect when executing a long-running batch. The default is 300 seconds.
Is the number of seconds before the login times out. The default is 15 seconds.
Specifies the number of bulk copy operations that can be performed in parallel. The maximum number of threads and ODBC connections that exist simultaneously is the lesser of MaxBcpThreads or the number of bulk copy requests that appear in the synchronization transaction in the distribution database. MaxBcpThreads must have a value greater than 0 and has no hard-coded upper limit. The default is 2 times the number of processors, up to a maximum value of 8. When applying a snapshot that was generated at the Publisher using the concurrent snapshot option, one thread is used, regardless of the number you specify for MaxBcpThreads.
Is the maximum number of push or pull transactions applied to Subscribers in one synchronization. A value of 0 indicates that the maximum is an infinite number of transactions. Other values can be used by Subscribers to shorten the duration of a synchronization being pulled from a Publisher.
If -MaxDeliveredTransactions is specified with -Continuous, -MaxDeliveredTransactions takes precedence. Synchronization continues until the number of transactions specified by -MaxDeliveredTransactions is reached, and then the Distribution Agent stops even though -Continuous is specified.
- -MessageInterval message_interval
Is the time interval used for history logging. A history event is logged when one of these parameters is reached:
If there is no replicated transaction available at the source, the agent reports a no-transaction message to the Distributor. This option specifies how long the agent waits before reporting another no-transaction message. Agents always report a no-transaction message when they detect that there are no transactions available at the source after previously processing replicated transactions. The default is 60 seconds.
Specifies the minimum size, in bytes, for binary large object data above which the data will be bound as a stream. You must specify –UseOledbStreaming to use this parameter. Values can range from 400 to 1048576 bytes, with a default of 16384 bytes.
Is the path of the agent output file. If the file name is not provided, the output is sent to the console. If the specified file name exists, the output is appended to the file.
- -OutputVerboseLevel[ 0| 1| 2]
Specifies whether the output should be verbose. If the verbose level is 0, only error messages are printed. If the verbose level is 1, all the progress report messages are printed. If the verbose level is 2 (default), all error messages and progress report messages are printed, which is useful for debugging.
Is the packet size, in bytes. The default is 4096 (bytes).
Is how often, in seconds, the distribution database is queried for replicated transactions. The default is 5 seconds.
Specifies an agent profile to use for agent parameters. If ProfileName is NULL, the agent profile is disabled. If ProfileName is not specified, the default profile for the agent type is used. For information, see Replication Agent Profiles.
- -Publication publication
Is the name of the publication. This parameter is only valid if the publication is set to always have a snapshot available for new or reinitialized subscriptions.
Is the number of seconds before the query times out. The default is 1800 seconds.
Specifies the quoted identifier character to use. The first character of the value indicates the value the Distribution Agent uses. If QuotedIdentifier is used with no value, the Distribution Agent uses a space. If QuotedIdentifier is not used, the Distribution Agent uses whatever quoted identifier the Subscriber supports.
Is a colon-separated list that specifies the error numbers to be skipped by this agent. For more information, see Skipping Errors in Transactional Replication.
Is the path to the Jet database (.mdb file) if SubscriberType is 2 (allows a connection to a Jet database without an ODBC Data Source Name (DSN)).
Is the Subscriber login name. If SubscriberSecurityMode is 0 (for SQL Server Authentication), this parameter must be specified.
Is the Subscriber password. If SubscriberSecurityMode is 0 (for SQL Server Authentication), this parameter must be specified.
- -SubscriberSecurityMode[ 0| 1]
Specifies the security mode of the Subscriber. A value of 0 indicates SQL Server Authentication, and a value of 1 indicates Windows Authentication Mode (default).
- -SubscriberType[ 0| 1| 3]
Specifies the type of Subscriber connection used by the Distribution Agent.
ODBC data source
OLE DB data source
- -SubscriptionStreams [0|1|2|...64]
Is the number of connections allowed per Distribution Agent to apply batches of changes in parallel to a Subscriber, while maintaining many of the transactional characteristics present when using a single thread. For a SQL Server Publisher, a range of values from 1 to 64 is supported. This parameter is only supported when the Publisher and Distributor are running on SQL Server 2005 or later versions. This parameter is not supported or must be 0 for non-SQL Server Subscribers or peer-to-peer subscriptions.
If one of the connections fails to execute or commit, all connections will abort the current batch, and the agent will use a single stream to retry the failed batches. Before this retry phase completes, there can be temporary transactional inconsistencies at the Subscriber. After the failed batches are successfully committed, the Subscriber is brought back to a state of transactional consistency.
Is the name of the subscription table generated or used at the given Subscriber. When not specified, the MSreplication_subscriptions (Transact-SQL) table is used. Use this option for database management systems (DBMS) that do not support long file names.
- -SubscriptionType[ 0| 1| 2]
Specifies the subscription type for distribution. A value of 0 indicates a push subscription, a value of 1 indicates a pull subscription, and a value of 2 indicates an anonymous subscription.
- -TransactionsPerHistory[ 0| 1|... 10000]
Specifies the transaction interval for history logging. If the number of committed transactions after the last instance of history logging is greater than this option, a history message is logged. The default is 100. A value of 0 indicates infinite TransactionsPerHistory. See the preceding –MessageIntervalparameter.
Must be specified as a parameter for a publication that allows data transformation.
Improves the performance of the initial snapshot by causing the Distribution Agent to use the BULK INSERT command when applying snapshot files to the Subscriber. This parameter is deprecated because it is not compatible with the XML data type. If you are not replicating XML data, this parameter can be used. This parameter cannot be used with character mode snapshots or non-SQL Server Subscribers. If you use this parameter, the SQL Server service account at the Subscriber must have read permissions on the directory where the snapshot .bcp data files are located. When this parameter is not used, the agent (for non-SQL Server Subscribers) or the ODBC driver loaded by the agent (for SQL Server Subscribers) reads from the files, so the security context of the SQL Server service account is not used.
When specified, enables the binding of binary large object data as a stream. Use -OledbStreamThreshold to specify the size, in bytes, above which a stream will be used.