http://blogs.msdn.com/jenss/archive/2009/04/28/a-long-but-not-missed-friend-revisited-prefixing-stored-procedures-with-sp.aspxComing as a simple sample with PBM (creating a policy with a condition that procedure names shouldn't´t start with SP_) and getting an interesting question in one of my classes, I wanted to revisit the question about the yet in some places existing namingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jenss/archive/2009/04/28/a-long-but-not-missed-friend-revisited-prefixing-stored-procedures-with-sp.aspx#9573157Tue, 28 Apr 2009 10:33:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:9573157Anith &raquo; A long (but not missed) friend revisited, prefixing stored procedures with SP_<p>PingBack from <a rel="nofollow" target="_new" href="http://www.anith.com/?p=33032">http://www.anith.com/?p=33032</a></p> http://blogs.msdn.com/jenss/archive/2009/04/28/a-long-but-not-missed-friend-revisited-prefixing-stored-procedures-with-sp.aspx#9727773Thu, 11 Jun 2009 23:51:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:9727773Andrew Zhu<p>This is not the case for SQL 2005 or SQL 2008.</p> <p>When procedure metadata is looked from catalog, if it is in dbo schema and name begins with sp_, we check if there is system procedures with same name and cache this fact.</p> <p>Later, we simply look up current database first, using this fact to avoid looking up system procedures.</p> <p>There should not be cache misss simply due to sp_ prefix naming, as this article describes.</p> <p>End users are not encouraged to use the sp_ prefix, unless the name will not likely be used by system procedures shipped with SQL Server in the future.</p> <p>Best Regards,</p> <p>Andrew Zhu</p> <p>[MSFT]</p>