Use SnapShot Relication or Use DT

  • When Do I need snapshot replication and

    when do I need DTS to Move Data

    I have Some Tables That are Located In The Central Site and are Rarely Updated (Less Than Once a month) .

    at the remote site these tables are not allowed to be updated .

    Do I need a snapshot replication or do I need a DTS Package that do the job Once a Month ?

  • Onther situation

    I Other Tables Are Rarely Updated In The Center But can be Updated at the remote site

    Does Snapshot replication take into account these changes and when the snapshot applied the changes are not beeing overrun?

  • For your first situation, if you are only interested in a few tables which are updated at one site only, transaction replication sounds best.

    If your data is being updated at two different sites, your only option is merge replication.

  • You could use transactional replication with immediate updating subscribers if you have reliable network links between the 2 servers.

    You also can use transactional replication with queue updates if you are using SQL 2K.

  • Well Snap Shot VS DTS

    Advantages off SnapShot

    1. Works On Extents (64K) IO

    2. Use Unsincronized Buffer Reading and Writing

    3.Ensure Accurate Schema Transfer.

    Disatvantege

    1. Relativly More Complicated.

    2. Has Limitation Of 255 Columns And 8000 Lenght

    DTS Advanteges

    1. Simpler To Define

    2. Can Be Defined Easly For Add Hock Transfers

    DisAtvnteges

    1.Works Sloly than SnapShot (8K) IO

    2.Some Times THe Schama Does Not Tranasfer Compleetly

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply