sqlserver20xxavailabilityenhancements-資料下載頁
2024-10-04 13:55本頁面
【正文】 B Enhancements Failover Clustering Enhancements PeertoPeer Replication Enhancements Mar2022 26 Microsoft Developer amp。 Platform Evangelism PeertoPeer Replication: Topology Changes SQL Server 2022 introduced PeertoPeer (or ?bidirectional?) transactional replication ? Great way to scale out a workload ? Partly as a way to have a redundant copy It had one major drawback – changing the PeertoPeer topology in any way required stopping ALL activity on servers in the topology SQL Server 2022 has REMOVED that restriction and also upgraded the PeertoPeer configuration wizard in SSMS Mar2022 27 Microsoft Developer amp。 Platform Evangelism DEMO PeertoPeer Replication: Topology Changes Mar2022 28 Microsoft Developer amp。 Platform Evangelism PeertoPeer Replication: Topology Wizard The wizard now is graphical, with dragndrop functionality for making topology connections Mar2022 29 Microsoft Developer amp。 Platform Evangelism PeertoPeer Replication: Topology Wizard Two catches still remain: 1. The option to configure a PeertoPeer topology still remains hidden until a Publication is switched to allow PeertoPeer subscriptions: 2. When adding a new node in the new Topology Wizard, you need to manually pick the Peer Originator ID (check mspeer_originatorid_history for previously used IDs): Mar2022 30 Microsoft Developer amp。 Platform Evangelism PeertoPeer Replication: Conflict Detection SQL Server 2022 adds conflict detection across a peertopeer topology ? All peer nodes must be running SQL Server 2022 Conflict detection managed by each row having a hidden column listing the originating peer node ID of the change The Distribution Agent on each node will detect conflicts by paring the hidden column Conflicts detected are: ? Insert – Insert ? Update – Update ? Insert/Update/Delete – Delete Mar2022 31 Microsoft Developer amp。 Platform Evangelism PeertoPeer Replication: Conflict Detection Conflict detection switched on by: ? Default when configured using SSMS ? Setting the @p2p_conflict_detection parameter of sp_addpublication to TRUE (default) ? Executing sp_configure_peerconflictdetection on all nodes AFTER a peertopeer topology has been setup When a conflict is detected, by default the Distribution Agent will stop applying changes ? This behavior can be changed by specifying TRUE for @p2p_continue_conflict in sp_addpublication ? Be careful: if set to TRUE, the Distribution Agent applies the change from the node with the highest node ID Correct by reinitializing the node or restarting the Agent Mar2022 32 Microsoft Developer amp。 Platform Evangelism Resources (1) Database Mirroring ? Blog Backup Compression ? Blog aspx Mar2022 33 Microsoft Developer amp。 Platform Evangelism Resources (1) HotAdd CPU ? Blog spx DBCC CHECKDB Failover Clustering PeertoPeer Replication ? Blog aspx Mar2022 34 Microsoft Developer amp。 Platform Evangelism Mar2022 35 Microsoft Developer amp。 Platform Evangelism
規(guī)章制度相關(guān)推薦
鄂ICP備17016276號-1