1 Chapter Overview Introducing Replication Planning for Replication

Download Report

Transcript 1 Chapter Overview Introducing Replication Planning for Replication

Chapter Overview
•
Introducing Replication
•
Planning for Replication
• Implementing Replication
•
Monitoring and Administering Replication
1
Reasons to Replicate
Information
•
Reducing network traffic between remote
locations and central server
• Separating OLTP and OLAP operations for
performance
•
Combining data from multiple locations
• Data redundancy
•
Supporting mobile users
•
Scaling out
2
Types of Replication
•
Snapshot
•
Transactional
• Merge
3
Replication Terminology
4
Snapshot Replication
5
Transactional Replication
6
Merge Replication
7
Physical Replication
Models
8
Replication Implementation
Tools
•
SQL Server Enterprise Manager and Replication
Monitor
• ActiveX controls, SQL-DMO, and Replication
Distributor Interface
•
System stored procedures
• Windows Synchronization Manager
•
Active Directory
9
Replication Security
Planning
•
Only sysadmin members can create and administer
replication.
•
Sysadmin and db_owner members can create and
configure publications.
•
Publisher uses the distributor_admin SQL Server
account to connect to remote Distributor.
•
•
Snapshot folder uses hidden admin share by default.
Agents run in security context of SQL Server Agent
by default and must have appropriate access rights.
10
Filtering Data
11
Initial Snapshot Options
•
Stored in Repldata folder on the Distributor by
default.
• Alternate locations include network drives or
compact disc, and files can be compressed using
CAP file format.
•
Maintaining snapshot files is optional, unless
anonymous Subscribers are permitted.
12
Distributor Configuration
•
Share with Publisher or use remote Distributor.
•
Use hidden admin share for snapshot folder, or
create explicit share.
•
Specify distribution database location, such as
RAID.
• Enable Publishers.
13
Publisher Configuration
•
Default vs. alternate snapshot folder.
•
Security context for replication agents.
• Enable security for remote Distributor.
•
Enable databases for replication.
•
Enable Subscribers.
14
Subscriber Configuration
•
Configure properties for replication agents
connecting to Subscribers.
• Specify security context for Subscriber
connection.
•
Specify schedule for Distribution and Merge
Agents.
15
Publication Creation
•
Specify updatable or transformable
subscriptions.
• Specify Subscriber types.
•
Specify articles and their properties.
•
Choose whether or not to list in Active Directory.
•
Configure horizontal and/or vertical filters.
•
Set schedule.
16
Push Subscriptions
•
•
Choose Subscribers, and select destination database.
•
•
Define subscription initialization properties.
•
For merge publications, define subscription priority
for conflict resolution.
•
Start required services.
Define Distribution or Merge Agent location and
schedule.
Configure updatable or transformable subscription
properties.
17
Pull Subscriptions
•
Locate publication using Active Directory, or locate
on registered servers.
•
•
•
Specify destination database.
•
•
Specify snapshot delivery information.
Specify named or anonymous subscription.
Specify updatable subscription properties, including
authentication.
Specify Distribution or Merge Agent schedule,
including on demand.
18
Replication Monitor
19
Distributor, Publisher, and
Publication Properties
•
Distributor properties, including retention
periods
• Publication properties, including subscription
expiration setting and status
•
New and existing replication agent profiles
• Subscription properties, including agent location
and status
20
Replication Conflicts and
Pull Subscription Properties
•
Microsoft Replication Conflict Viewer
•
Windows Synchronization Manager
• Alternate synchronization partners
•
Subscriber, Publisher, and Distributor login
properties
•
Enabling interactive resolution
21
Chapter Summary
•
Replication uses the Publisher – Distributor –
Subscriber metaphor.
•
•
Choose snapshot, transactional or merge replication.
•
Choose subscription type based on performance
requirements and administrative convenience.
•
Consider enabling interactive conflict resolution
for merge replication.
Understand security context issues for replication
agents.
22