Post reply

Upgrading server w/ t-byte data

  • March 28, 2012 at 3:18 pm

    #270928

    Hi--

    I haven't posted in a bit, but I'd like some advice. I have been asked to update a database server from sql server 2000 to sql server 2008. There are more than 40 databases on the server totaling about 1.5 terra in size. The update is pretty straightforward with only a few dts packages to convert, but I have a limited maintenance window--12 to 24 hours and I'm a bit nervous about being able to restore all of this.

    Suggestions for getting these back up pronto?

    Thanks in advance--

    Jim

  • March 28, 2012 at 3:49 pm

    #1466057

    Any chance of bringing up a new server and migrating the data instead?

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

  • March 28, 2012 at 4:02 pm

    #1466067

    Jeff--

    That is still a topic of discussion with the hardware folks and the checkbook folks. 🙂 I suspect that the answer will be no and that's why I'm in search of plan 9 from outerspace.

    Thx --Jim

  • March 28, 2012 at 4:09 pm

    #1466071

    That's a lot of data, but I'll second what Jeff said, a second server to migrate to would be my ideal choice.

    It was extenuating circumstances, but I have used replication to ease a complex migration (slightly different platforms in my case, but same idea). SQL Server 2000 SP3 can participate in replication with SQL 2008. Cutover was as simple as removing replication and redirecting clients to secondary server.

    You could also explore log shipping to achieve the same effect.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 28, 2012 at 4:38 pm

    #1466081

    replication is not a bad idea. I'll check with the person coordinating the vendors and see if it might be an issue. This will be coming to fruition in the next three weeks or so, and I'll either post our solution or my better half will post my obit 😀

    Thanks guys--

  • March 28, 2012 at 4:45 pm

    #1466085

    Obit? Hopefully it does not come to that! 😛

    If you get shot down on hardware for the second server know that you can replicate or log ship to different instances running on the same server.

    Godspeed!

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 28, 2012 at 7:40 pm

    #1466131

    Have you considered doing a side by side install, then just detach and attach the databases?

    This way you can migrate DB by DB (or in related groups) and test at each step. No restore needed.

    As a roll back you would have to have backups and a log backup chain but you would only need to roll back those databases up to the point of failure. Planning the order you migrate in will be important depending on you own criteria. e.g. largest first, or most critical first, or least critical first etc.

    You'll also have to take into account that you'll now have a named instance.

    Cheers

    Leo

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

Viewing 7 posts - 1 through 6 (of 6 total)

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