Newbie - How to Do This (if Possible)

  • Hi Members:

    I have never used replication before so please excuse my ignorance. Here's the situation:

    I have set up various sql2000 databases on my client's server (SBS2000). Every month, I remotely access their server (through PCAnywhere) and obtain their database so I can perform statistical analysis on the data.

    Currently, what I do is detach the existing database from my end, then use file transfer to grab the database (which can take forever) from my client's server, and then re-attach it on my end.

    I'm thinking to myself: There must be an easier way to do this - uh, maybe through replication!  Both my client and I are running our own SBS 2000 servers, and I have not a clue how I can do this (or if it's even possible). If it is, can you please point me in the right direction (in terms of an article on how to achieve this)?

    Many thanks in advance!

    Justin

  • You could either implement Replication or just create a DTS Package to copy and restore the Database periodically. With Replication, have a look in BOL on how to implement and configure Replication, there is ample info in BOL. Then we can help if you get stuck.


    Kindest Regards,

  • I don't think replication is the way to go on this. 

    If you are doing stats analysis then this, plus your comment about copying files, suggests that your dataset is huge.  I am also not sure what your connection is like or how secure it is, but I wouldn't want to try snapshot replication on a huge dataset unless I absolutely had to.

    Transactional replication has a timeout on its transactions so unless you want frequent connects to your clients system I don't think this is the way to go.

    Personally I would have a batch job at the client end to ftp the most recent backup of the relevant databases to your ftp location.  That way the client computer need not be shut down to allow you to get a copy.

    When I was doing stats analysis I used to receive a monthly tape of 20Gb of information in SQL6.5 format which I had to DTS into a SQL2000 server.

    There was no disruption at the client end.  There were only two problems with this.

    • Snail mail to get the tape.
    • The SQL6.5 restore could go squiffy and 20Gb takes a long time to load.
    • Users baying for blood because you can't transfer and process 20Gb in the time it takes them to dring a cup of coffee.

Viewing 3 posts - 1 through 3 (of 3 total)

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