Post reply

Import and Export

  • May 28, 2010 at 12:46 pm

    #140631

    Hi,

    We have Server A for production with SQL server 2005 EE x64 with SP3 and Server B for reporting with SQL Server 2005 Developer x86 with SP3.

    Now I need to refresh the data from Server A to Server B daily. Currently, I'm backing up the databases in Server A and copy to Server B and restore. But the problem here is the database size. We have 2 databases with Size of 70 GB.

    The copying of 170 GB from Production taking a lot time and I came to know that we should not copy such a large files from production.

    So I'm looking for other options:

    Can I use Export from Server A and import to server B? How can I achieve this?

    Thanks

  • May 28, 2010 at 1:21 pm

    #1174104

    Replication or Log Shipping come to mind. Log Shipping is probably the simplest.

    You could export/import the data, but that might be cumbersome and take a while.

  • May 28, 2010 at 1:33 pm

    #1174107

    If you have a SAN, see if it has the ability to do a "SAN Clone" or "SAN Snapshot". We did that at one company I worked at. 1TB DB updates in < 2 minutes is a real "Martha Stuart Moment". 😀

    --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)

  • May 28, 2010 at 1:44 pm

    #1174111

    So Import/Export is NOT meant for this kind of data refresh right?

  • May 28, 2010 at 2:09 pm

    #1174124

    passivebyz (5/28/2010)

    So Import/Export is NOT meant for this kind of data refresh right?

    Not really.

    Something to note: log shipping leaves the backup server in a read-only state. And if not set up correctly, will boot everyone out when it goes to restore the transaction logs.

    Along with replication, you might also want to investigate mirroring.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

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

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