As outlined in knowledge base article 263889 (Description of SQL Server blocking caused by compile locks http://support.microsoft.com/kb/263889) it says you should specify the owner when calling
a stored procedure to reduce compile locks. I've tried this out in SQL Server 2000 by calling a stored procedure without an owner. As expected in the profiler I can see a CacheMiss then a ExecContextHit.
However, if I try exactly the same thing in SQL Server 2005 I never see a CacheMiss event (unless the execution plan needs to be created), I always see a CacheHit first. Is this something that's been improved in SQL Server 2005? The knowledge
base article says it applies to 2005 at the foot of the page but I can't see it.
Thanks for your help.
View Complete Post