| 1. | For more information on queued updating subscriptions , see
有关排队更新订阅的详细信息，请参阅 |
| 2. | For more information about queued updating subscriptions , see
有关排队更新订阅的详细信息，请参阅 |
| 3. | Microsoft message queuing msmq option for queued updating subscription
排队更新订阅的microsoft消息队列( msmq )选项 |
| 4. | Microsoft message queuing msmq option for queued updating subscriptions
排队更新订阅的microsoft消息队列( msmq )选项 |
| 5. | If a transactional publication supports queued updating subscriptions , replication adds the column
如果事务性发布支持排队更新订阅，复制就会向每个表添加 |
| 6. | This applies to transactional publications that are enabled for queued updating subscriptions a value of true for the
之前执行。这适用于为排队更新订阅启用的事务性发布（ |
| 7. | How to : view data conflicts for transactional publications with queued updating subscriptions sql server management studio
如何查看包含排队更新订阅的事务性发布的数据冲突( sql server management studio ) |
| 8. | In sql server 2000 , immediate and queued updating subscribers did not allow updates to any of the large data types
在sql server 2000中，立即更新订阅服务器和排队更新订阅服务器不允许对任何大型数据类型（ |
| 9. | Subscribers to oracle publications cannot use immediate updating or queued updating subscriptions , or be nodes in a peer - to - peer or bidirectional topology
Oracle发布的订阅服务器不能使用立即更新订阅或排队更新订阅，也不能作为对等或双向拓扑中的节点。 |
| 10. | To track changes , merge replication and transactional replication with queued updating subscriptions must be able to uniquely identify every row in every published table
若要跟踪更改，带有排队更新订阅的合并复制和事务性复制必须能够唯一地标识每个已发布表中的每一行。 |
