Chapter 12: Designing a Data- Archiving Solution MCITP Administrator: Microsoft SQL Server 2005...

Chapter 12: Designing a Data-Archiving Solution

MCITP Administrator: Microsoft SQL Server 2005 Database Server

Infrastructure Design Study Guide (70-443)

Reasons for Archiving Data

• Improved query performance

• Decreased disk space use

• Reduced maintenance time

• Reduced costs

© Wiley Inc. 2006. All Rights Reserved.

Steps to Create a Data Archive Plan

1. Determine business and regulatory requirements

2. Determine what data to archive

3. Select storage format

4. Develop a data-movement strategy

5. Design a replication topology if replication is used


Determine business and regulatory requirements

• Establish how much data needs to remain online

• Identify busines requriements that determine length data needs to be reatined either online or in archive

• How much of the data is needed? Can summary tables be used?

• What is accessibility of data needed?• What regulatory requirements are

relevant


Determine what data to archive

• Identify obsolete data

• Determine if archiving produces a savings in disk space cost

• Determine if there are performance benefits

• Establish the archiving interval


Sructuring Archival Data

• Structure by using the following types of tables:– Partitioned tables– Normalized tables– Denormalized tables– Indexed views– Summary Tables


Guidelines for Choosing Which Structure to Use

• Data Accessibility Requirements

• Storage costs


Select Storage Format

• Type of Storage format:– Magnetic tape– Optical media– Physical disks

• Dedicated or shared server?


Factors Effecting Storage Format Choice

• Cost

• Accessibility

• Shelf life

• Reliability & durability

• Securioty

• Changing technology


Develop a Data-Movement Strategy

• Describes how archival data is moved from production to archive

• Considerations should include:– Frequency of data movement– Minimizing impact on production– Direct or indirect transfer– Security of data during movement– Data verification processes


Replication Topology

• Defines relationship between servers and copies of data

• Dsignin should include:– Whether replicated data needs to be updated

and by whom– Data distribution needs– Replication environment– Types of replications– How replication type and topologies align


Replication Roles

• Publisher

• Distributor

• Subscriber

• SQL Server can be one, two or all three


Replication Components

• Article

• Publication


Replication Model Considerations

• Autonomy

• Latency

• Consistency


Types of Replication

• Transactional

• Snapshot

• Merge


Snapshot Replication

• Copies entire publication to subscribers each replication

• Created using Snapshot Agent

• Used primarily to establish the initial set of data


Transactional Replication

• Standard Transactional Replication

• Transcational Replication with Updating Subscribers

• Peer-to-Peer Transactional Replication


Merge Replication

• Most complex, most flexible

• Allows changes at both publishers and subscribers

• Conflicts are problem but resolvable


Managing Replication Topology

• Develop and test a backup and restore strategy• Script the replication topology• Understand replication performance parameters• Establish performance baseline• Create thresholds and alerts• Monitor the replication topology• Validate data on periodic basis• Adjust publication and distribution retention

periods when necessary• Understand how to modify publications if

application requirements change


Designing a Replication Strategy

• Determine requirement for replication with archival data

• Select a replication type• Create a replication topology

diagram• Determine subscribers, distributors

and publishers• Select pull or push subscription• Determine security requirements


Chapter 12: Designing a Data- Archiving Solution MCITP Administrator: Microsoft SQL Server 2005...

Documents

Transcript of Chapter 12: Designing a Data- Archiving Solution MCITP Administrator: Microsoft SQL Server 2005...