I just recently configured a brand-new Windows SBS 2008 Server with SQL 2008.

The box is a HP Proliant DL 380 G5 with 32GB RAM and a 250GB SSD.

I have Access97 as a front-end and using ODBC I connect to SQL Server databases via linked tables. Actually does work very well.

After the initial install, SQL performance was stellar. Then, after doing a Windows Update and installing many updates, the SQL performance dropped terribly. It seems to me an update has caused an issue.

Does anyone know of key updates that might compromise the SQL performance?

  • 4
    This wall of text is quite difficult to digest; care to make it more readable, and ask a real question while you are at it? Any particular reason why you're installing SQL Server 2008 in 2019? – mustaccio Apr 25 at 1:22
  • 2
    "Just installed" an eleven-year old product? Why, oh why. SQL Server 2008 will be unsupported by the end of July. – Max Vernon Apr 25 at 1:50
  • 1
    1) OK, I really thought I was asking a "real" question. ??? Let me try again "Is there an update that might be known that causes SQL performance to tank?" Some people who have installed software like mine say "KBxxxxxx" has known issues... etc. 2) The reason I am installing SQL Server 2008 in 2019 is I own SQL 2008 and not 2019. Running a small business with limited resources and funds as well as not changing software that is actually working (save for this re-build of the same style server) is cost-effective. I googled that tens of thousands of people like me still use SBS 2008. – Russ Apr 25 at 12:51
  • I think I might have stepped on many feet here by me asking a question of prehistoric software. Wow, so sorry. As to the idea that SQL 2008 or any MS product was ever "supported" is kind a joke to me. Am I to think I can contact MS directly and get straight and useful answers? If so, then why do we need forums like this? – Russ Apr 25 at 12:56
  • 2
    Look into "tcp chimney offload" and disable all relevant features thatyou can AND make sure you're running the latest network adapter driver. It's likely that your network drivers are quite old since you're on Windows 2008, and drivers from that era were notorious for offload feature bugs killing network throughput. – Tony Hinkle Apr 25 at 13:53

Seriously, do yourself a favor and get an updated, supported version of SQL Server. As in SQL Server 2016+.

Of course, you won't actually do that right now, so start troubleshooting poor performance in a methodical manner using the tools SQL Server provides.

  1. Check for blocking.
  2. Check wait stats.
  3. Ensure the SQL Server instance is configured with an appropriate setting for "max server memory", "max degree of parallelism", and "cost threshold for parallelism"

Follow the great directions here: https://www.mssqltips.com/sqlservertip/4111/first-steps-for-sql-server-performance-troubleshooting/

  • The odd thing is I really do not think spending $$$ upgrading and installing an de-bugging 2016+ software will help. I have 2 identical machines save for a few MS updates that has caused SQL to be dog-slow. We are only talking about the simplest table with less than 50k records. SELECT Customer.* FROM Customer ... that is it. It seems the ODBC connection is agonizingly slow. If I run this from the server through SMS, all it super-fast. – Russ Apr 25 at 13:00
  • Thanks for sharing the troubleshooting tools. That may come in handy. As mentioned and after 100's of hours of pulling my hair out, I think it all boils down to something has messed with the ODBC connection and MS Access. – Russ Apr 25 at 13:02
  • Sorry for all this bother....I will figure it out on my own as it seems that if I do not have the latest and greatest version then I am sure no one really is interested in this apparently isolated yet reproducible issue. I vote to delete this question as it seems to serve no one. Is there a moderator out there? – Russ Apr 25 at 13:04

Not the answer you're looking for? Browse other questions tagged or ask your own question.