Post reply

In place upgrade

  • September 28, 2009 at 9:37 am

    #139215

    Hi

    Could anyone please tell me whether it is necessary to double the disk space for the data and log file drives before making an in-place upgrade from SQL Server 2000 to SQL Server 2005?

    Also could you please tell me if there are caveats for the in place upgrade process from SS 2000 to 2005.

    Thank You,

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 9:39 am

    #1059061

    No need to double the disk space.

  • September 28, 2009 at 10:07 am

    #1059076

    Make sure you have good backups.

    The data files and log files will get attached to the new instance when it's upgraded, and they'll be migrated to the new formats as needed. They don't get copied over. you lose your old copy, and once this is done, you cannot uninstall 2005 and go back to 2000. You'd need to restore from your 2000 backups.

  • September 28, 2009 at 10:10 am

    #1059078

    Hi Ravikanth,

    Thank you very much for your reply.

    Actually I have seen that in a MCITP certification book. That book says that we should reserve 2-4 times the actual disk space during the upgrade process.

    In our company we are doing an inplace upgrade from SQL Server 2000 to SS 20005. I was little bit confused by that statement in that MCITP book. So, I thought it would be better to ask real time experts in SSC forums.

    Thank You,

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 10:13 am

    #1059079

    Hi Steve,

    Thank you very much for your reply.

    Currently, we are planning to take backups before doing the upgrade.

    Thank You,

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 10:21 am

    #1059084

    Be sure to double check your sql2000 settings (config + security) before starting the upgrade.

    In case of DRP, you may have to start from sql2000 again, so if you don't have an inventory of os-level grants, features on/off,...

    Search at SSC, this topic has been couvered a couple of times.

    (In place upgrade)

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • September 28, 2009 at 10:25 am

    #1059086

    Make sure you run Upgrade advisor before the upgrade.

    Disable all trace flags and maintenance jobs.

    Make sure your SQL 2000 is atleast have build number 2000.80.760 or later.

    Backup all system and user db`s.

    Also are there any DTS packages?

  • September 28, 2009 at 10:46 am

    #1059097

    Hi ALZDBA,

    Thank you very much for your reply.

    Could you please tell me what is DRP and how to note those settings?

    Thank you,

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 10:49 am

    #1059098

    Hi Ravikanth,

    Thank you very much for your reply.

    Could you please tell me which trace flags have to be disabled ?

    Thank You,

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 10:54 am

    #1059101

    All existing trace flags.

  • September 28, 2009 at 11:14 am

    #1059105

    DRP is typically disaster recovery plan. Be ready in case you create your own disaster. Know what exact build number you have, and you may want to script out jobs/alerts/packages to be safe.

    I would remove all trace flags you have, but note which ones and what they're for. The numbers may have changed for 2005, or they may not be needed.

  • September 28, 2009 at 11:18 am

    #1059106

    Hi Ravikanth,

    Thank you very much.

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 11:21 am

    #1059107

    Hi Steve,

    Thank you very much for your reply.

    I really appreciate your help.

    Best Regards,

    SQLBuddy.

  • September 28, 2009 at 11:56 pm

    #1059316

    Steve already couvered the DRP part.

    Just to add a little bit to Keep in mind:

    - SQL2005 has many features "off by default" on a fresh install. If you perform an in place upgrade from an earlier version, the installation process will activate the needed options, to be sure everything will keep on working.

    - SQL2005 is more strict (granular) on os-level authorisation.

    - If you have (scheduled) dts packages, be sure you know what an upgrade does to your packages !

    ( install downward compatibility packages for dts, in case it cannot translate all to SSIS, because it wil "port" the dts package as an object on itself)

    - Don't choose an in place upgrade, because that seems to be the easy way !

    - as already stated, you should start with "sql2005 upgrade advisor". This tool will point you to potential issues on many levels.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • September 29, 2009 at 1:09 pm

    #1059688

    Hi ALZDBA,

    Thank you very much for such a nice and detailed reply. I really appreciate your help.

    Thank you once again!

    Best Regards,

    SQLBuddy.

Viewing 15 posts - 1 through 15 (of 18 total)

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