Post reply

Too much for too little

  • June 28, 2011 at 7:39 pm

    #252741

    Hi,

    I work on a sql server 2000 database at office and then at my residence.

    Till now, when the database size was small enough, I used to do a full backup at one place, take it on my pen drive and restore it at the other. Work on the database there and repeat the above sequence.

    The database size has now grown and the backup itself is now more than 1 GB.

    During each work session, I insert / update only a few rows in only a few tables.

    Is there no alternative to carrying a 1 GB backup to and fro everyday??

    Both the database servers are not connected to each other, so i guess replication is not the idea. But I might be wrong.

    What would be the best solution to this?

    Thanks

  • July 15, 2011 at 2:23 am

    #1353241

    You are right. Replication is not possible if the servers are not connected.

    Differential/Log backup is ideal for your scenario.

  • July 15, 2011 at 8:23 pm

    #1353799

    Nilesh Deshpande (6/28/2011)

    Hi,

    I work on a sql server 2000 database at office and then at my residence.

    Till now, when the database size was small enough, I used to do a full backup at one place, take it on my pen drive and restore it at the other. Work on the database there and repeat the above sequence.

    The database size has now grown and the backup itself is now more than 1 GB.

    During each work session, I insert / update only a few rows in only a few tables.

    Is there no alternative to carrying a 1 GB backup to and fro everyday??

    Both the database servers are not connected to each other, so i guess replication is not the idea. But I might be wrong.

    What would be the best solution to this?

    Thanks

    If you're in the FULL recovery mode (and you probably are... everyone forgets it), are you backing up the log file to keep it from just holding every row you ever inserted, deleted, or modified? If not, I'll bet that's your problem.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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