Post reply

Data for development and report development

  • June 28, 2012 at 6:17 am

    #263503

    Besides a restore of PROD to a DEV\Report build environment what is the best way to transfer this data to this environ with the least amount of pressure on PROD? The environment needs to have some DB's as RO for reprot development and some DB's RW for development and code testing. While not ideal for many reasons, currently we restore 2TB of data a night from PROD. Replication seems to be an option with unwanted pressure on PROD publishers. Mirroring and then snapshots seems to be an option for RO DB's. Any additonal options would be appreciated.

  • June 28, 2012 at 6:34 am

    #1506557

    If you have a decent SAN, many SANs will either come with or you can buy an option to do what I call "SAN snapshots". Even on a 2 TB system, the time to update something like a reporting or dev server can be meaured in seconds rather than minutes.

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

  • June 29, 2012 at 7:07 am

    #1507112

    VM offers snapshots & Lab Manager to do this sort of stuff. We use differential backups and some nifty bak & log shipping automation to give devMonkeys & reportDonkeys what they want. Key was to make sure they understood they were not going to be workign with anything near realtime data so we could stage our crap where we wanted and when they pressed buttom for what they wanted only the restore time was what they saw...

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

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