Subscription Validation Options (Transactional Subscriptions)
Applies to: 
SQL Server
Azure SQL Database
Use the Subscription Validation Options dialog box to specify whether validation should use a row count only, or a row count and a binary checksum.
Note
Azure SQL Managed Instance can be a publisher, distributor, and subscriber for snapshot and transactional replication. Databases in Azure SQL Database can only be push subscribers for snapshot and transactional replication. For more information, see Transactional replication with Azure SQL Database and Azure SQL Managed Instance.
Options
Verify that the Subscriber has the same number of rows of replicated data as the Publisher
Select the type of row count validation to perform. For Oracle publications, the only available option is Compute an actual row count by querying the tables directly.
Compare checksums to verify row data
In addition to taking a count of rows at the Publisher and Subscriber, a checksum of all the data is calculated using the binary checksum algorithm. If the row count fails, the checksum is not performed.
Stop the Distribution Agent after the validation has completed
By default, the Distribution Agent runs continuously. Select this option to stop the agent after validation is performed. This allows you to check whether validation was successful before continuing to replicate data to the Subscriber.
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for