replication and log shipping

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Eric

    replication and log shipping

    Hi, Ive a few questions and would be grateful for any
    assistance/comments from experience as Ive not that much dba
    experience , we have 3 servers all containing sql 2000 standard
    edition, two (prod and standby) located in the U.S. and Im hoping to
    set up the third as a reporting server locally in Europe...presum ably
    having the data close as possible and as current as possible for
    reporting?...We dont have the resources to implement clustering so
    presumably I envisage keeping the standy server using either Log
    shipping or replication (i think log shipping being the best approach
    here?). My question is whats the best approach for getting the data
    across the network from the U.S to Europe (differing domains but
    internal network).. Is transactional replication albeit push or pull
    the best approach to get the data across, ie. with log shipping it
    seems that you will have to copy across the bckups nightly using xcopy
    /ftp transaction log backups scheduled, does transactional replication
    just propogate the changes and not the entire backup daily. if its
    just the changes does it note just the changes made to the standby
    server every day and just replicate these across? (i.e. a backup
    restore is done daily with log shipping to the standby server..With
    transactional replication will it note that some of this data has been
    replicated already..) Any help greatly appreciated..
    Eric
Working...