Standard to Enterprise, In-Place or New Installation

  • We are currently running SQL Server 2008 R2 Standard x64

    We have to move to SQL Server 2008 R2 Enterprise x64 to take advantage of TDE

    The server in question is highly unused right now so either way is a possibility.

    My IS wants me to do an upgrade, I always prefer a new installation, does anyone have any information about disadvantages, problems, concerns with an In-Place upgrade?

    We need to get 2 servers running on Enterprise, one being for our testing environment the other being for production.

    My recommendation was to build a new server, deploy that to our testing environment

    Rebuild the current standard server and new install of enterprise that becomes our new production.

    In addition, I'd like to know if there is a way to set a policy that any new databases that get installed are required to be encrypted.

  • I would recommend the New install. Top reason for me is in case a need to roll back or access that old system can quickly be achieved.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • You really do not have an option for an in-place upgrade. You do have an option for an SKU Upgrade.

    I would recommend the SKU Upgrade - it is quite simple. Basically, you run the setup with SKUUPGRADE option (command line).

    Note: if you have any CU's applied you will have to apply them after the SKUUPGRADE since that will take you back to the RTM version (unless you have slip-streamed the installation media).

    I would only recommend creating a new instance and moving the databases if there are issues with the initial installation and configuration (e.g. LUNs not setup correctly, system database on C:\ drive, etc...).

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • New Installation is a better option

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • New instance and migration of databases!


    [font="Times New Roman"]rfr.ferrari[/font]
    DBA - SQL Server 2008
    MCITP | MCTS

    remember is live or suffer twice!
    the period you fastest growing is the most difficult period of your life!
  • The database is the least concern of mine, we have a script to rebuild it and then would re-run the job to populate the data.

    This is a healthcare data deduplication database which detects multiple medical records of the same patient and then sends a report to the customer of their duplicates for them to cleanup.

    My next concern is how do I enable a policy that every database on that server is required to be encrypted with TDE?

  • Jeffrey Williams-493691 (5/26/2011)


    You really do not have an option for an in-place upgrade. You do have an option for an SKU Upgrade.

    I would recommend the SKU Upgrade - it is quite simple. Basically, you run the setup with SKUUPGRADE option (command line).

    Note: if you have any CU's applied you will have to apply them after the SKUUPGRADE since that will take you back to the RTM version (unless you have slip-streamed the installation media).

    I would only recommend creating a new instance and moving the databases if there are issues with the initial installation and configuration (e.g. LUNs not setup correctly, system database on C:\ drive, etc...).

    This is a good recommendation - I had forgotten about the skuupgrade.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • You can use policies to check for TDE. Use the EncryptionEnabled property of the database facet. You won't be able to use this to prevent someone from not enabling TDE, but you can schedule the policy to check and return which dbs are not encrypted.

    Thanks,

    Mwise

  • Thank you everyone for your responses on the upgrade, I just met with our IS staff and they have agreed to build new servers for us.:-D

    I'm still looking for ideas on the enforcement of TDE databases, I'll look at the policy comment posted a few minutes ago once I have the server built (ETA Monday, June 9) but other ideas are gladly accepted and very much appreciated.

    I LOVE SQL Server Central Forums!

  • I wanted to update everyone on this topic.

    My IS staff insisted an in-place upgrade was possible, so I hesitantly agreed to give it a shot.

    It worked simply. Just select maintenance from the install window GUI and go through the questions, quick and easy.

    I did very the server upgraded by select @@version and in fact it now shows Enterprise.

  • that's right!!!


    [font="Times New Roman"]rfr.ferrari[/font]
    DBA - SQL Server 2008
    MCITP | MCTS

    remember is live or suffer twice!
    the period you fastest growing is the most difficult period of your life!

Viewing 11 posts - 1 through 10 (of 10 total)

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