Post reply

Performance on Windows 2003

  • September 22, 2004 at 2:19 am

    #86421

    We have 2 servers, both 2-processor Xeon machines with 2Gb of ram.

    Both servers have Windows 2003 Enterprise installed on it.

    Machine A is our application server and machine B is the database server holding an installation of SQL Server 2000 Enterprise.

    When executing queries from A to B with Query analyzer, or from our application, it takes approx. 5-10 seconds before we get a result.

    When replacing machine A with a Windows 2000 Server, the queries are executed 10-100 times faster.

    Are there any known issues regarding this problem ?

    Thanks in advance

    Yoeri

    btw, Network performance is a non-issue, it has a GB network.

    [update] No difference when using Windows authentication

  • September 23, 2004 at 6:17 am

    #524138

    My experience is that there are 2 most likely possibilities:

    1) The W2003 DB server is very badly tuned and is running slowly.  This is unlikely, unless your site has done some serious tinkering with Windows default settings.  However, it is worth checking how much memory SQL is allowed to use (via EM) and making sure there is enough left for W2003. Remember that W2003 needs a good 100MB more than W2000 to run smoothly.

    2) The network card in one or both W2003 servers have not been set up correctly.  Get your network people to check duplex and packet size settings, and make sure they match the settings on the routers and firewalls, etc.  We have had some horrendous performance problems on various NT4, W2000, W2003 servers because these have not been set correctly. 

    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

  • September 23, 2004 at 6:21 am

    #524139

    Thanks for the reply ... our people are busy tuning the network ... we discovered that pinging took also too long

    It is obviously a network configuration problem

  • September 23, 2004 at 8:30 am

    #524192

    I always blame the network

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

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

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