Post reply

Upgrading

  • March 8, 2007 at 8:14 am

    #119173

    So we are thinking of upgrading from SQL 2000 to SQL 2005. I found an upgrade advisor on the Microsoft website and wonder if it is a usefull tool. Has anyone experience with it? Does it give a decent 'advise'?

    I am also interested in articles or sites dealing with upgrading, experiences and advise based on real miogrations, if possible. We are going from server to server, so techbically it is not an upgrade.

    Basically I am asking: are the recommendations given by Microsoft good ones?

    Greetz,
    Hans Brouwer

  • March 8, 2007 at 10:28 pm

    #693995

    It is the only tool which checks HW and SW and database recomendations....

    Read the following articles which will help you in your upgrade...

    http://msdn2.microsoft.com/en-us/library/ms144256.aspx

    http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

    http://searchsqlserver.techtarget.com/generic/0,295582,sid87_gci1188595,00.html

     

    MohammedU
    Microsoft SQL Server MVP

  • March 8, 2007 at 11:08 pm

    #694001

    The SQL Server Upgrade Advisor will tell you exactly what will break and what you should start to migrate towards things that will go away in the future.

    It will analyze your stored procedures, databases, hardware and software and let you know if those will break in the upgrade.  It will also take a workload file from SQL Profiler if you have one and analyze any ad-hoc queries that are used on the database within your workload file to tell you if those will break any applications that may be using the database.

    It's pretty good at narrowing down where you need to focus efforts for your upgrade.

     

    Christopher Ford

  • March 9, 2007 at 5:41 am

    #694050

    I think the Upgrade Advisor uses the features in the RTM version of SQL 2005 as a target.  It will not tell you about restrictions added in fixes since RTM.  The main one I have found is a change to job step token syntax described in KB 915845, but this may not affect you.

    If you plan to use DTS on SQL 2005, also check KB 917406 - our site did not fit the criteria for the problem but we needed the fix!

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • March 9, 2007 at 4:11 pm

    #694204

    I found the upgrade advisor useful. It let me know what syntax needed to be changed in order for our sprocs to work with 2005. 

  • March 10, 2007 at 4:35 am

    #694228

    Tnx for all answers. It is really helpful.

    Greetz,
    Hans Brouwer

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

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