<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8211560\x26blogName\x3dTech+Tips,+Tricks+%26+Trivia\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://mvark.blogspot.com/search\x26blogLocale\x3den\x26v\x3d2\x26homepageUrl\x3dhttp://mvark.blogspot.com/\x26vt\x3d-5147029996388199615', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Tech Tips, Tricks & Trivia

by 'Anil' Radhakrishna
An architect's notes, experiments, discoveries and annotated bookmarks.

Search from over a hundred HOW TO articles, Tips and Tricks


Why do stored procedures recompile?

When SQL Server stored procedures recompile, it is not always good news for performance conscious developers and to identify the potential issues, SQL Profiler can be used.

The SP:Recompile event in SQL Profiler shows when a stored procedure or a trigger is being recompiled.

In SQL Server 2000 SP2 or in SQL Server 2005, the SP:Recompile event identifies the reason for the recompilation with an integer code in the EventSubClass column. Here is a list of the integer codes with the reason for recompilation:

SQL Server 2000 SP2

Integer code - Reason for recompilation
-----------------------------------------------------------------------
1 - Schema, bindings, or permissions changed between compile or execute.
2 - Statistics changed.
3 - Object not found at compile time, deferred check to
run time.
4 - Set option changed in batch.
5 - Temp table schema, binding, or permission changed.
6 - Remote rowset schema, binding, or permission
changed.


SQL Server 2005

Integer code - Reason for recompilation
-------------------------------------------------
1 - Schema changed.
2 - Statistics changed.
3 - Recompile DNR.
4 - Set option changed.
5 - Temp table changed.
6 - Remote rowset changed.
7 - For browse perms changed.
8 - Query notification environment changed.
9 - MPI view changed.
10 - Cursor options changed.
11 - With recompile option.

Labels:

Tweet this | Google+ it | Share on FB

« Home | Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »

»

Post a Comment