Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am facing a performance problem on our server. The main reason seems the versions of OS and SQL Server. Once I install the SQL Server 2008 on Windows Server 2008 R2, the response time of my web site becomes very slow. Whereas, if I use SQL Server 2008 on another machine which has Windows Storage Server 2003 R2, the response time is much faster.

Both operating systems have the latest updates, do you have any idea of this contradiction? or did anyone experiencing similar problem about new updates to Windows Server 2008 R2 which is running SQL Server 2008?

Thanks, cas

share|improve this question

migrated from Nov 15 '10 at 21:18

This question came from our site for professional and enthusiast programmers.

Presumably the two servers you mention are identical relative to hardware (memory, CPU, disk configuration)? By "slow" I assume you mean response time between mouse clicks/ENTER? – jl. Nov 15 '10 at 22:58

I faced a similar issue in the past, with the the same SO and Sql Server version, with a particular DB. My problem was related to the transaction log, i needed to backup/clean it and also needed to free some more space in th drive and after i really could notice the performance going up again.

I don't knwow if by any chance this might be your situation.


share|improve this answer

Do any of the symptoms in MS KB918483 apply to your situation?

share|improve this answer

Sounds eerily familiar to what StackOverflow went through. Are you running Dell servers? We hit the same issue ourselves on new servers running Windows 2008 R2. The Windows 2003 servers were fine. Once we updated the BIOS settings on 2008 performance kicked up considerably.

share|improve this answer

99% of the time the slowdown will have nothing to do with the host OS but something within the database. Usually the statistics have become stale and the SQL Server isn't generating good execution plans.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.