Post SQL Server 2000 Service Pack 4 Performance Issues

By:   |   Updated: 2007-04-24   |   Comments   |   Related: More > Upgrades and Migrations

Please do not scroll away - stay informed.
Dear Database Professional,

Did you know that publishes new SQL Server content on a daily basis as well as offers free webinars and tutorials?

Let us help you stay informed and learn something new each day. Click here to keep informed.

Thank you,
Greg Robidoux and Jeremy Kadlec ( Co-Founders)

My company has recently upgraded to SQL Server 2000 Service Pack 4 and we have experienced significant performance issues.  Overall our performance baseline has dropped significantly (more than 50%) immediately after the service pack installation.  We need to correct our performance issue, determine the problematic symptoms and the root cause in the service pack.  How should we do so?


In researching this issue further take the following steps to address the item:

  • Captured performance metrics to determine the worst performing queries
  • Researched the individual queries to determine the root cause
  • Determined that table scanning was occurring frequently in queries post SQL Server 2000 Service Pack 4
  • Determined the cause of the table scanning as implicit conversions of mismatched data types
  • Data types do not match between the embedded T-SQL in the front end code\stored procedures to the views and to the base tables
    • In some examples the implicit conversion and data type mismatch problem was related to the following:
    • The implicit conversion performed a table scan as opposed to using an index as was the case with SQL Server 2000 Service Pack 3

To resolve the immediate issue, take the following steps:

  • Identify the data types mismatches and correct them in logical groupings in order to properly test the application
  • Correct the data type mismatches starting from the tables, then the views, next move on to the stored procedures and embedded T-SQL code in the front end to ensure the data types are consistent
  • Review the query plans to ensure the expected indexes are being used following the code changes
  • Perform both functional and load testing on the new versions of the code
  • Perform some basic maintenance tasks
Next Steps

Get Started Now - Click here to get your free 14 day trial of SolarWinds Database Insights

get scripts

next tip button

About the author
MSSQLTips author Jeremy Kadlec Jeremy Kadlec is the Co-Founder, Editor and Author at, CTO @ Edgewood Solutions and a six time SQL Server MVP.

View all my tips

Article Last Updated: 2007-04-24

Comments For This Article

get free sql tips
agree to terms