Pop Quiz: SQL 2000 Bug or SQL 2017 Bug?

2002: Me and Bailey, mom’s Great Dane

When I was thinking about this site’s 17th birthday, I started wondering: back in 2002, what bug might I have been working with in SQL Server?

I started reading back to the list of bugs fixed in SQL Server 2000 Service Pack 1, and it hit me…these bugs aren’t all that different than the ones we’re facing today.

Before you click on each bug, guess whether it was in SQL 2000 Service Pack 1, or last month’s SQL Server 2017 CU14. When you click on each one, you’ll see the release notes for it. (Unfortunately, the 2000 bugs all point to the SP1 page – the individual bug pages have been lost to the sands of time.) Good luck!

  1. CREATE for existing object with IDENTITY column causes duplicate IDENTITY values
  2. Statistics maintenance causes significant bottleneck on SQL Servers that use 16 or more CPUs
  3. Assertion failure occurs when you try to back up database in limited disk space
  4. TCP Timeout or login time-out error occurs when you connect to SQL Server using Integrated Authentication
  5. Error removing log shipping on secondary when database name has a quote
  6. Upgrade fails with an error when sysadmin account “sa” is renamed
  7. SQL Server resource DLL may fail to log to the event viewer in a cluster
  8. Configuration option network.enablekdcfromkrb5 now set to false instead of true
  9. SELECT may not return all rows if it contains a large number of values in an IN clause on a NUMERIC column
  10. Query results are not as expected when you run a particular query from Excel
  11. Complex DISTINCT or GROUP BY query can return unexpected results with parallel execution plan
  12. “Non-yielding” error occurs when there is a heavy use of prepared statements
  13. INSERT statement incorrectly conflicts with constraint
  14. DBCC STACKDUMP doesn’t generate dump file
  15. Combination of multiple EXIST, OR, and subquery clauses may give a sub-optimal plan (you know, I’m gonna go out on a limb and say that still happens)
  16. Incorrect record is deleted or updated when a clustered index is in descending order
  17. Assertion occurs when a parallel query deletes

Let me know how you did in the comments.

Previous Post
Updated First Responder Kit and Consultant Toolkit for April 2019
Next Post
Are your CPU-intensive queries running slowly? Check your VM type.

7 Comments. Leave new

  • Michael J Swart
    May 1, 2019 11:03 am

    I did no better than random. Each one was a complete guess.
    “Incorrect Record is Deleted or Updated When a Clustered Index is in Descending Order” was the one that caught my eye. It reminded me of the time when I ran our automated tests against a local database where I reversed the order of every index. I was looking for places where we assume results order without an order by and I found more than I expected.

    Reply
  • KAMIL NOWINSKI
    May 1, 2019 3:46 pm

    Brent, that was really good exercise. My answers were maybe on 50% right (or bad). Is that mean I supposed to back to work with MS Access? 😉

    Reply
  • Wow, 13 out of 14! I got #4 wrong. Your note on #15 was a bit of a giveaway too, I reckon I would’ve guessed that as 2017 without it 😀

    Reply
  • Derek Bell
    May 6, 2019 4:48 am

    Got 9 right, which is no better than flipping a coin.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu
{"cart_token":"","hash":"","cart_data":""}