Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Upgrading from SQL Server 2000 Expand / Collapse
Posted Thursday, July 26, 2012 10:23 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, December 28, 2013 5:45 PM
Points: 94, Visits: 96
I have a great deal of stored procedures and data integration that need to be optimized. All the SQL code was written for SQL Server 2000 and 2005. But now we just got off SQL Server 2000. What are some easy ways to optimize code (assuming they exist) now that SQL Server 2000 is out of the picture?
Post #1336235
Posted Monday, July 30, 2012 9:33 AM



Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 7,745, Visits: 13,878
It is nice you can leverage some of the T-SQL improvements now that you have completely moved off 2000. However, while your perspective might be tilted towards "we just moved off 2000 to 2005" that does not affect the rules for optimizing SQL Server database code. Google "optimize sql server code" and you will find plenty of information on improvements that can be made, and things to look for in your codebase to make it better.

There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1337339
Posted Tuesday, July 31, 2012 6:14 AM

SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 9:28 AM
Points: 4,909, Visits: 7,190
1) I hope you updated ALL statistics (index, column, etc) with a FULL SCAN immediately after upgrade. That is a MANDATORY step.

2) Most tuning will come exactly like it did in SQL 2000 - aggregate profiler runs.

3) It is MUCH easier to do wait stats and file IO stall analyses now, and both of those should be a primary tool to find where it hurts on a wider scale.

4) sp_whoisactive: get it, learn all of it's goodness. it is documented inside the code and Adam Machanic did a 30-day blog post series on

5) LOTS of Dynamic Management Views to help you. There are some good books about using them for tuning. Performance Tuning with SQL Server Dynamic Management Views for example, and Troubleshooting SQL Server - A Guide for the Accidental DBA. There are numerous more advanced books too, as well as a bunch of free eBooks.

6) Consider getting a performance tuning professional on board to give your systems and applications a review. Probably lots of low-hanging fruit can be found and fixed plus you would gain the invaluable benefit of being mentored by a guru on how to do effective tuning analysis and refactoring.


Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1337834
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse