带有 SqlNotificationRequest 的服务代理
我正在为我的项目评估具有 SQL 通知的 Service Broker。我的要求是用户从系统 A 下订单，它将更新订单表。一旦下订单，我需要通知系统 B。我已经使用 Trigger 、 Service Broker 和 SQLNotificaiton ADO.NET 完成了快速 POC。它按我的预期工作。
我想了解该小组的什么信息 A）为此我需要遵循哪些最佳实践？ B) 上述方法有什么缺点（如果有的话）？ C) 使用触发器有什么缺点吗？如果是的话，上述方法的内容是什么？
订单表每天会从系统A获取1000到1500个订单。我也想知道上述方法的性能。
I am in the process of evaluating a Service Broker with SQL noticiation for my project. My requirements is User places a order from System A and it will update Order Table. As soon as order is place i need to notify the System B. I have done a quick POC with Trigger , Service Broker and SQLNotificaiton ADO.NET. It is working as i expected.
What i would like to know the group
A) What are the best practices i need to follow for this?
B) What are disadvantages with the above approach if any?
C) Are there any disadvantes of using the Triggers? If so what are those for above approach?
The order table will get order from System A like 1000 to 1500 every day. I also would like to know the performance of above approach.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您想要做的只是将数据从系统 A 推送到系统 B，那么只要没有客户端连接到系统 B，您就不需要 Sql 通知。
您可以考虑使用更改跟踪，而不是使用触发器。查看Service Broker 团队博客上的“实时数据集成...” 文章。
If what you're trying to do is simply push data from System A to System B, then as long as there are no clients connected to System B, you won't need Sql Notification.
Instead of using triggers you may consider Change Tracking. Take a look at "Real Time Data Integration..." article on Service Broker Team Blog.