您要查找的是不是:
- Tables included in a merge publication cannot also be published as part of a transactional publication that allows queued updating subscriptions. 合并发布中包含的表也不能作为允许排队更新订阅的事务发布的一部分进行发布。
- With queued updating subscriptions, changes from Subscribers are written to a queue; changes are then read from the queue and delivered to the Publisher by the Queue Reader Agent. 利用排队更新订阅,将订阅服务器中的更改写入队列;然后,队列读取器代理从该队列中读取更改并将其传递到发布服务器。
- After a publication is enabled for updating subscriptions or queued updating subscriptions, the option cannot be disabled for the publication (although subscriptions do not need to use it). 为更新订阅或排队更新订阅启用发布后,不能再为发布禁用该选项(即使订阅不需要使用它)。
- Creates triggers at the Subscriber used with all types of updatable subscriptions (Immediate, Queued, and Immediate Updating with Queued Updating as Failover). 在订阅服务器上创建与所有类型的可更新订阅(立即、排队和将排队更新作为故障转移的立即更新)一起使用的触发器。
- SSE does not support queued updating using pull subscriptions. SSE不支持使用请求订阅进行排队更新。
- Governs how the triggers for immediate updating subscriptions execute calls at the Publisher. 参数控制即时更新订阅的触发器如何在发布服务器上执行调用。
- Provides automatic generation at the Subscriber of article custom stored procedures and triggers that support updating subscriptions. 在包含项目自定义存储过程和支持更新订阅的触发器的订阅服务器上提供自动生成。
- In addition to the general considerations for subscriptions, there are a number of considerations for updating subscriptions. 除了要注意订阅的常规注意事项外,还要注意许多更新订阅的注意事项。
- If queued updating is used, the changes are stored in a queue; the queued transactions are then applied asynchronously at the Publisher whenever network connectivity is available. 如果使用排队更新,更改将存储在队列中;当网络连接可用时,再在发布服务器中异步应用排队事务。
- Queued updating: updates made at the Subscriber are stored in a queue. 排队更新:将订阅服务器中的更新存储在队列中。
- If the publication allows immediate updating subscriptions and an article in the publication has a column filter, you cannot filter out non-nullable columns without defaults. 如果发布允许立即更新订阅,且发布中的项目具有列筛选器,则无法筛选出无默认值的不可为空的列。
- In addition to the general considerations for subscriptions, there are a number of considerations for updating subscriptions for transactional replication. 除了要注意订阅的常规注意事项外,还要注意许多事务性复制的更新订阅的注意事项。
- You cannot drop the rowguid column from articles in merge publications or the mstran_repl_version column from articles in transactional publications that support updating subscriptions, because they are used by replication. 无法从合并发布的项目中删除rowguid列,也不能从支持更新订阅的事务性发布的项目中删除mstran_repl_version列,因为这些列由复制使用。
- If immediate updating or queued updating options are used with transactional replication, updates can be made at the Subscriber, and with queued updating, conflicts might occur. 如果事务性复制使用了立即更新或排队更新选项,更新可以在订阅服务器中进行,对于排队更新,可能会发生冲突。
- What is Update Subscription Service? 什么是产品更新服务?
- Auction update subscriptions and breaking news alerts are examples of applications that should use event rules. 拍卖更新订阅和动态新闻警报都是应使用事件规则的应用程序示例。
- Although updates can be made at multiple participating databases, it is important to understand that peer-to-peer topologies do not require or allow the immediate or queued updating publication options. 虽然可以在多个参与的数据库中进行更新,但是请务必了解:对等拓扑不需要或不允许立即或排队对发布选项的更新。
- On the Login for Updatable Subscriptions page, specify a linked server over which connections to the Publisher are made for immediate updating subscriptions. 在“用于可更新订阅的登录名”页上,指定链接服务器,通过此服务器可与发布服务器建立连接,以便立即更新订阅。
- For merge replication and transactional replication with updatable subscriptions, identity columns should be managed automatically by replication. 对于合并复制和具有可更新订阅的事务性复制,标识列应该由复制自动管理。
- Security Considerations for Updating Subscriptions 更新订阅的安全注意事项