Day 8 Part 1 Replication

Replication
Topics
• SQL Server Replication Review
• Concepts, terminology
• Snapshot Replication
• Transactional Replication
• Change tracking and forwarding
• Deployment examples
• Merge Replication
• Summary
What Is SQL Server Replication?
• Replicates database objects

• Keeps the data synchronized
• Maintains 1 to 1 data row relationship
• Optionally subsets or transforms data
• Can push or pull data to destination
• Utilizes a Publish and Subscribe paradigm
Publish/Subscribe Paradigm
• Publication:
• Defines a group of source database objects to replicate
• The individual database objects are identified as publication
“articles”
• Subscription:
• Defines subscriber as a destination for data flowing from the
specified source publication
• Filters – row and column
• Static filters define data partition during publication creation
and apply to all future subscriptions
• Dynamic filters are calculated during synchronization and
allow data filtering on a per subscriber basis.
Publishers And Subscribers
Servers (SQL Server, Oracle, Other)
Laptops (SQL Server, MSDE)
odbc/ole-db
Publisher/Distributor
Handhelds (SQL Server CE)
(SQL Server)
Subscribers
Common Replication Scenarios
• Offloading query workload

• Web data caching
• Data warehouse staging
• Reporting
• Warm standby/geographic fail-over
• Mobile clients
• Data consolidation and distribution
• Heterogeneous system integration
Types Of Replication
• Point in time set of data created using bulk copy API
• Used for replicating non-volatile data sets like price lists
• Delivers initial data for transactional and merge replication
• Targets well connected, server to server, low latency
replication of data
• Row changes are replayed in original order, preserving
transactional consistency
• Designed for occasionally connected applications
• Delivers net data changes with row by row conflict
resolution
Topics
• Summary
Snapshot Replication
Snapshot
Agent
Files containing
schema and data
Publishing Published Distribution
Database Tables Agent
Subscribing
Database
• Subscriber gets a complete copy of published data

• Snapshot can be scheduled during off peak hours
• Options
• Configure a custom pre or post-snapshot script
• Specify CAB compression of files
• Specify FTP for delivering snapshot files
• The snapshot step for transactional and merge publications can be bypassed if the
initial data already exists at the subscriber (nosync)
demo
Topics
• Summary
Transactional Replication
Snapshot
Agent
Files containing
schema and data
Publishing Published Distribution
Database Agent
Tables
Subscribing
Database
DB
log Logreader Distribution
Agent Database
• Distribution Agent delivers initial snapshot of data prepared by

Snapshot Agent
• Logreader Agent reads changes from database log
• Logreader Agent stores changes in the Distribution database
• Distribution Agent forwards changes to subscribers
Change Tracking – Log Reader
• SQL Server marks transactions in log for replication

• Log Reader reads last transaction id processed for a publisher
from distribution database
• Retrieves next set of transactions and SQL statements from
publisher log
• Writes SQL statements to distribution database
• Advances replication watermark in the log to coordinate with
the log manager of the database engine
• Writes history and error information into the distribution
database
Forwarding – Distribution Agent
• The Distribution Agent reads the last transaction

received by the subscriber
• Retrieves the next set of transactions and SQL
statements from the distribution database
• Applies changes to subscriber
• Updates the last transaction received
• Note: agent can run on the distributor (“push”) or
on the subscriber (“pull”)
Change Tracking - Updating Subscribers
Publisher
Queue
2PC, RPC Distributor Queue Reader Agent

NETWORK
Queue
Immediate Updating Read-Only Queued Updating

Subscriber Subscriber Subscriber
Change Tracking And Forwarding - Features
• Low overhead at publisher

• Partial updates to BLOBS
• Built in validation option
• Automatic cleanup of store and forward queues
• Options for managing constraints at subscriber (NFR)
• Identity range management
• Indexed view support
demo
Topics
• Summary
Reporting Server/DW Staging
OLAP
Tokyo
Cube
Subscriber
Redmond
OLTP Server Reporting Server London
Publisher Subscriber and Subscriber

Re-Publisher
• 75%+ of typical online DB activity is selecting data!

• Will reduce load and contention on OLTP server
• Improves adhoc query performance and tuning options
Web Data Caches
Updates
Load Balancing
Replication
Publisher
Distributor
Internet Clients
App Server Tier Read Only Data Tier Updatable Data Tier
(Subscribers) (Publisher)
Data Consolidation And Distribution
Subscriber
Publisher
London
Subscriber
Publisher Subscriber
Publisher
Tokyo
Redmond Subscriber
Publisher
New Delhi
Creating A Warm Standby Server
• Why replication and not log shipping?

• Continuous read access to the replica
• Lower latency
• Mirroring a subset of the original DB
• Otherwise use log shipping
• First choice for maintaining warm standby
• All databases changes replicated
• Less overhead and easier to fail back
Topics
• Summary
Merge Replication
Change Tracking
Publishing Merge Subscribing

Database Process Database
Default or Custom
Resolver
• Net row changes tracked by system triggers in publishing and

subscribing databases
• Merge Agent propagates changes between publishing and
subscribing databases
• Conflicts are detected and resolved automatically
Merge Replication
Change Tracking Metadata
• Generation – watermark that groups changes

• Row Lineage: Maintains sequence of changes to a row
• Represents the identity of all replicas that modified the row, and which
version they made
• Detect simultaneous changes, subsequent changes and dampen sync loops
• Column Versions: Who updated the column, and when
• For every column, stores identity or replica that made last update, and the
version
• Attribute level tracking – merge changes to disjoint columns
Merge Replication
Key Features
• Dynamic subscriber data partitions

• Customizable conflict resolution
• HTTP sync with SQL Server CE
• In-line validation of data
• Synchronization to alternate publishers
Merge Replication
Dynamic Subscriber Partitions
Goals
• Eliminate or reduce the possibility of conflicts.
• Minimize the volume of data maintained at client
• Improve performance over a slow link
• Prevent clients from receiving sensitive data
Implementation
• Vertical partitions - Column filters on tables
• Horizontal partitions
• Subset filters on individual tables
• Join filters according to relationship between tables
• Both static and dynamic partitioning can be supported
Merge Replication
Conflict Resolution
• Source Wins
• Changes sent to destination
• Destination wins
• Discard changes and rely on next phase to propagate winner
• Generate new row
• E.g., Additive Resolver
• Update destination and propagate changes during next phase
to source
• Customizable
Merge Replication
HTTP sync with SQL Server CE
SQL Server CE SERVER

Server SQL SQL Server
Client Server Replication
Agent I Agent SQL
App I Reconciler Provider
DB
S Message
Replication
Provider
Device
DB
.IN .OUT
demo
Merge Replication
Topics
• Summary
Merge Replication
Deployment
• Mobile applications
• Sales Force Automation
• Distribution Applications
• Inventory Tracking
• Catalog Servers
• Regional servers that make offline local updates with shared
data
• Incident tracking/Call Center applications
• Example: Microsoft RAID bug database
Merge Replication Example
Sales Force Automation Topology
Central Publisher
West Coast
East Coast
HQ Regional Managers
Regional Regional
Server Server
Regional
Server
Mobile Users
Mobile Users
Sales Office
Sales Office
Mobile Users
Merge Replication
Server To Server - MSN Search Example
Catalog 2
Catalog 1
Catalog 3
• Typically data is not partitioned

• Will provide better connectivity to client applications
in a given region
• Servers are mostly offline and sync regularly over a fast reliable link
Merge Replication
Distribution Apps
SQL Server
Connection Publisher
http IIS Server
Firewall Firewall
• HTTP synchronization
• Typically data is partitioned for each user
• Number of devices syncing with the server is large
Putting It All Together…
Internet customers
Web data caches

Eastern sales force
East region server

HQ
Western sales force OLTP Server
West region server
Suppliers with heterogeneous databases

DW staging Warm Standby
Reporting server
server
Server
Assignments
• Practice and ENJOY 

Thank You

Day 8 Part 1 Replication

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Day 8 Part 1 Replication

Încărcat de

Drepturi de autor:

Formate disponibile

Replication

• Replicates database objects

Servers (SQL Server, Oracle, Other)

Laptops (SQL Server, MSDE)

• Offloading query workload

• Subscriber gets a complete copy of published data

• Distribution Agent delivers initial snapshot of data prepared by

• SQL Server marks transactions in log for replication

• The Distribution Agent reads the last transaction

2PC, RPC Distributor Queue Reader Agent

Immediate Updating Read-Only Queued Updating

• Low overhead at publisher

OLTP Server Reporting Server London

Publisher Subscriber and Subscriber

• 75%+ of typical online DB activity is selecting data!

• Why replication and not log shipping?

Publishing Merge Subscribing

• Net row changes tracked by system triggers in publishing and

• Generation – watermark that groups changes

• Dynamic subscriber data partitions

SQL Server CE SERVER

• Typically data is not partitioned

http IIS Server

Web data caches

East region server

West region server

Suppliers with heterogeneous databases

• Practice and ENJOY 

S-ar putea să vă placă și