您要查找的是不是:
- 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 更新訂閱的安全注意事項