Identifying Deprecated SQL Server Code with Profiler

By: Jeremy Kadlec   |   Read Comments (2)   |   Related Tips: More > Deprecated Features

Problem
In your recent tip (WARNING: SQL Server Deprecated Features) you have outlined a number of deprecated features.  The listing with the mapping to the new code set is beneficial.  Unfortunately I have an enterprise SQL Server environment and I need to be able to identify the deprecated features in more of an automated manner.  We do not have the time to check all of our code (stored procedures, functions, etc.) and I know we have T-SQL embedded in middle tier and front end applications.  How can I analyze this code in an efficient manner?

Solution
In any sized environment, identifying the deprecated SQL Server features could be a long and time consuming process.  Luckily, Microsoft was thinking ahead and has events in Profiler that can be captured to identify the code with deprecated features.  Let's take a look at how to capture the T-SQL code:

Next Steps

• As you begin to analyze your environment for a migration to SQL Server 2005 or 2008, be sure to keep the deprecated features in mind.
• Be sure to understand the mapped T-SQL commands to be able to continue business operations.
• To streamline the identification of the deprecated features consider using SQL Server 2005 Profiler.
• Check out these related tips:
  • WARNING: SQL Server Deprecated Features
  • Capturing Graphical Query Plans with Profiler
  • Capturing Deadlock Information in XML Format
  • SQL Server Performance Statistics Using a Server Side Trace
  • Correlating Performance Monitor and Trace Data
  • Deprecation Final Support Event Class
  • Deprecation Announcement Event Class

 

Last Update: 11/9/2007

About the author

Jeremy is the CTO @ Edgewood Solutions, co-founder of MSSQLTips.com and SQL Server MVP since 2009.

View all my tips

We Recommend

• More SQL Server DBA Tips...

Comments and Feedback:

Thursday, September 16, 2010 - 9:54:26 AM - Tony Henley	Read The Tip
To be proactive, do you need to run profiler on the SQL Server version, to which you are migrating? (i.e you are on SQL 2008 and want to migrate to SQL 2008 R2, so you should run profiler on SQL Server 2008 R2?)

Thursday, September 16, 2010 - 11:50:52 AM - Admin	Read The Tip
Tony, Good question.  In this circumstance, you want to run the code on the SQL Server 2008 instance. Thank you, The MSSQLTips Team

Post a Comment or Question

Keep it clean and stay on the subject or we may delete your comment.
Your email address is not published. Required fields are marked with an asterisk (*)

*Name

*Email

Notify for updates Signup for our newsletter

Comments *** NOTE *** - If you want to include code from SQL Server Management Studio (SSMS) in your post, please copy the code from SSMS and paste the code into a text editor like NotePad before copying the code below to remove the SSMS formatting.
*Enter Code

 

Sponsor Information

Find and fix SQL Server problems before they happen - SQL diagnostic manager now with predictive analysis! Get your SQL Server database under version control now! Find out why... What grade do you think your SQL Servers get? Find out with Edgewood's Health Check consulting services. Unlock the power of the Transaction log to discover unauthorized changes and recover lost data Free Webinar - Backup compression and storage deduplication: A perfect match?