验证复制的存储过程
有谁知道验证事务复制中实际代码的正确存储过程？我有一个基本上是 select * from table1 的视图。我将该视图更改为 select * from table2 在发布者中，并且复制监视器中存在错误（应该有），但是当我运行 sp“sp_publication_validation”时，它会进行验证。
Does anyone know of the correct stored procedure that validates the actual code in transactional replication? I have a view that basically is a select * from table1. I changed that view to select * from table2 in the publisher and there is an error in the replication monitor (as there should be) but when I run the sp "sp_publication_validation" it validates.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
sp_publication_validation 在发布者和订阅者处执行行计数和/或校验和检查，并比较两个结果。如果它们比较相同，则该文章被认为是“好”，如果不同，则被认为是“坏”。现在，您的视图如何适应您的复制设置？您的观点是否以文章形式发表？如果是这样，那么 sysarticles（在发布者处）中 schema_option 的值是多少？另外，复制监视器中出现什么错误？
sp_publication_validation does a row count and/or checksum check at the publisher and subscriber and compares the two results. If they compare as the same, the article is considered "good" and if not, it's considered "bad". Now, how does your view fit into your replication setup? Do you have the view published as an article? If so, what is the value for schema_option for it in sysarticles (at the publisher)? Also, what error are you getting in the replication monitor?