Post reply

64 bit sql server responding slow

  • May 16, 2007 at 3:49 pm

    #116811

     

    I have a 32 bit sql 2000 server & another 64 bit sql 2005 server.

     

    I have restored a backup on my 64 bit server from 32 bit & all other system db’s as well.

     

    After restoring suddenly my db is responding slow, I tries configuring all possible memory options & update STATISTICS as well, but no luck.

     

     

    ------------
    Prakash Sawant

    http://psawant.blogspot.com

  • May 17, 2007 at 10:54 am

    #707219

    Hi Prakash,

    I made the same experiences tho months ago.

    Try to reorg/recreate your indexes and your stored procedures.

    Did you change the compatibility level of your database to 90 for SQL 2005? This is necessary to use the features of SQL 2005.

    Why did your restore the system databases? This is dangerous, because in SQL 2005 exist other structures in master and msdb. It is not necessary to restore them from SQL 2000. If you added custom objects to your system DBs you should implement them in the new system dbs in SQL 2005.

    If you have indexes in your tables with increasing values (e.g. datetime) you should often use the update statistics statement because these auto updates do not work properly in SQL 2005. Maybe this is fixed now.

    You have to secure that your SQL Server gets enough RAM under 64 bit. Check which processes use how much RAM and do not give it back. You can (and you should) specify how much RAM SQL Server should use as minimum. If you then restart your machine this amount of RAM will be grabbed by SQL Server. Other than in a 32 bit system under 64 bit you have often the problem, that all processes try to get as much RAM as possible and never give it back (if the machine is not restarted)

     

    Best regards,

    Stefan

     

    Kindest Regards,

    SK

  • May 17, 2007 at 12:31 pm

    #707233

    Hi Stefan,

    I tried recreating Index every thing, but no luck.

    I think what you said about the system db might be true, but not sure as of now how much that will affect my performance.

    If i don't find any thing then i might have to rebuild the server again and try it step by step.

    Thanks for your help.

     

     

     

     

    ------------
    Prakash Sawant

    http://psawant.blogspot.com

  • May 18, 2007 at 3:25 am

    #707357

    If you have restored a SQL 2000 master database to SQL 2005 and got SQL 2005 to start, then well done!  Just don't expect it to perform well or for it to provide all of the SQL 2005 functionality.  There are many changes in the data structures of master between SQL 2000 and SQL 2005.

    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

  • May 18, 2007 at 4:10 am

    #707368

    You have messed up .

    Please go ahead and rebuild the Server, then restore the SQL 2000 Database with the system databases.

    Regards,

    Minaz Amin

     

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

  • May 18, 2007 at 4:12 am

    #707369

    I mean without the System database.

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

  • May 18, 2007 at 12:24 pm

    #707562

    Hi All,

    Thanks for your help.

    The problem is solved now, their where 2 problems.

    One with server Ethernet port, never would have guessed unless saw some lost packets. The other one was with collation settings.

     

    ------------
    Prakash Sawant

    http://psawant.blogspot.com

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

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