Microsoft Sql Server 2000 Transactional Replication Enhancements

Microsoft SQL Server 2000 Transactional Replication Enhancements

Transactional Replication Model


Apply initial snapshot at Subscribers
Data is modified at the Publisher Changes are storedin distribution database







Distribution agent move changes to Subscribers
2

When to Use


You need to maintain transactional consistency
Subscribers are connected to thePublisher most of the time Require low latency for Subscribers receiving changes





3

Some New Features
      

Concurrent snapshot Improved error handling More options forvalidating replicated data Publish data and database objects Queued updating subscriptions Transform published data Enhanced database restore options

4

Concurrent Snapshot
 

Allow datamodifications during snapshot
Version requirements for using concurrent snapshots Reduce duration of share locks



5

Concurrent Snapshot (2)


How concurrent snapshots are applied
Use NOT FORREPLICATION on constraints



6

Skip Specified Errors


For Distribution Agent
Use Continue On Data Consistency Errors Distribution Agent profile Use –skiperrors parameter Use withcaution
7







Validation of Replicated Data


Comparison of data between Publisher and Subscribers
Validation Method Rowcount SQL Server™ 2000  SQL Server 7.0  SQL Server 6.5 Checksum
Binary Checksum






8

Validation of Replicated Data (2)


Text or image columns Locks on the tables during validation sp_publication_validation --> sp_article_validation -->sp_table_validation
9





Publishing Database Objects


Allow replication of more types of database objects
Publishing indexed views as tables Differs for each replication model



10

Queued Updating


Allow subscribers to modify published data without an active network connection to the publisher
Store subscriber changes in a queue Conflicts and conflict...