Post reply

Migration from SQL SERVER 2000 to SQL SERVER 2005

  • July 31, 2006 at 12:43 am

    #169780

    Dear friends,

    we have already databases under SQL Server 2000. Before we migrate all these databases to SQL Server 2005, we seek for advices in this forum.

    1. does migration of table, stored procs, etc need much manual change in SQL Server 2005 ?

    2. we also have application (Visual VB .NET 2003) of course with connection to SQL Server 2000,

    do we have to change the connection code so we can connect to SQL Server 2005 ?

    3. how big transactions and scale are supported by SQL Server 2005 ? as you know nowadays, banking sector still uses mainframe, middleframe like AS/400 instead of computer server .....

    can SQL Server 2005 handle heavy and huge transactional like ATM, credit, fuel stations ?

    thanks

    hendy

  • July 31, 2006 at 3:22 am

    #652304

    Hi Hendy,

    a SQL Server 2000 to 2005 migration should not require any manual changes of tables, stored procs unless you have code that directly accesses system objects that have been changed or if you used any code that has been deprecated in SQL 2005.

    You will not have to change the connection code to connect to SQL 2005 - unless of course you use a different server name.

    SQL Server is very scalable and can handle over 1 million transactions per minute.  Assuming you have the hardware and money.  Check out Microsoft's benchmark page, http://www.microsoft.com/sql/prodinfo/compare/benchmarks.mspx

    With regards to the migration, use the upgrade advisor.  Plan for the upgrade and test it.  It should be relatively straight forward but you should still run a test upgrade to make sure you don't get any nasty surprises.

    Karl
    source control for SQL Server

  • August 2, 2006 at 2:08 am

    #652751

    Hi,

    I totally agree with Karl. No need to change to the tablesor store proc even the connection string.Last month we did migration from SQL 2000 to SQL 2005 which was very smooth. Yes after, database migration please run DBCC UPDATEUSAGE to correct any invalid counts.

    This DBCC statement corrects the rows, used pages, reserved pages, leaf pages and data page counts for each partition in a table or index. For more information, see DBCC UPDATEUSAGE (Transact-SQL).Have a nice day!!!

    Links for review:

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

    Thanks

    Minaz

    "More Green More Oxygen !! Plant a tree today"

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

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