Replication Log Reader Agent Utility
The Replication Log Reader Agent utility configures and begins the Log Reader Agent, which monitors the transaction log of each database configured for replication, and copies the transactions marked for replication from the transaction log into the distribution database.
Note Parameters can be specified in any order. When optional parameters are not specified, values from predefined registry settings on the local computer are used.
Displays usage information.
Is the name of the Publisher. Specify server_name for the default instance of Microsoft® SQL Server™ 2000 on that server. Specify server_name\instance_name for a named instance of SQL Server 2000 on that server.
Is the name of the Publisher database.
Is the number of buffers available for asynchronous transactions. The default is 2. Increasing the number of buffers can improve performance because doing so reduces memory paging; however, a larger number of buffers also increases the amount of memory reserved for paging. Evaluate performance by seeing how a change in buffer values affects the speed of the connections between Subscriber and Distributor.
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.
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. Specify server_name for the default instance of SQL Server 2000 on that server. Specify server_name\instance_name for a named instance of SQL Server 2000 on that server.
Is the Distributor login name.
Is the Distributor password.
Specifies the security mode of the Distributor. A value of 0 indicates SQL Server Authentication Mode (default), and a value of 1 indicates Windows Authentication Mode.
Specifies the amount of history logged during a log reader operation. You can minimize the performance affect of history logging by selecting 1.
|HistoryVerboseLevel value|| |
|1||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.|
|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.|
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 increased to avoid having the checkup agent mark the Log Reader 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.
Requires Service Pack 1 or later. MaxCmdsInTran specifies the maximum number of statements grouped into a transaction as the Log Reader writes commands to the distribution database. Using this parameter allows the Log Reader Agent and Distribution Agent to divide large transactions (consisting of many commands) at the Publisher into several smaller transactions when applied at the Subscriber. Specifying this parameter can reduce contention at the Distributor and reduce latency between the Publisher and Subscriber. Because the original transaction is applied in smaller units, the Subscriber can access rows of a large logical Publisher transaction prior to the end of the original transaction, breaking strict transactional atomicity. The default is 0, which preserves the transaction boundaries of the Publisher.
Is the time interval used for history logging. A history event is logged when one of these parameters is reached:
- The TransactionsPerHistory value is reached after the last history event is logged.
- The MessageInterval value is reached after the last history event is logged.
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.
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.
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 log is queried for replicated transactions. The default is 2 seconds.
Specifies the security mode of the Publisher. A value of 0 indicates SQL Server Authentication (default), and a value of 1 indicates Windows Authentication Mode.
Is the Publisher login name.
Is the Publisher password.
Is the number of seconds before the query times out. The default is 300 seconds.
Is the maximum number of transactions read out of the transaction log of the publishing database. The default is 500.
-ReadBatchThreshold number of commands
Is the number of replication commands to be read from the transaction log before being issued to the Subscriber by the Distribution Agent. The default is 0. If this parameter is not specified, the Log Reader Agent will read to the end of the log or to the number specified in -ReadBatchSize (number of transactions).