Celebrating the first day of Summer with the first technical post on the blog since mid-Winter (apologies for my absence)..
Jens has a great post regarding the internal behavior of various forms of sp_-named programmability objects. Some SQLRAP-related research led me to take a different tack, and I wanted to share the results of that research here as well.
So here are five things about sp_ to be aware of. I’ve verified all of these behaviors on SQL Server 2000 and above (through SQL Server 2008 R2).
So -- surprisingly enough on a Microsoft-hosted SQL Server blog -- my recommendation is that you leave the sp_ object names to Microsoft, and use one of the workarounds discussed above to implement a naming convention which behaves consistently across your instance.
The headaches you save will likely be your own.
Does your shop have any rules regarding use of sp_? Do you have any stories to tell -- good or bad -- about using it with user-created objects?
Contact me if you have any questions or comments, or if you’d like simple repro scripts which demonstrate these concepts.
this copyrighted material was originally posted at http://blogs.technet.com/wardpond.
the author and his employer are pleased to provide this content for you at that site, and via rss, free of charge and without advertising.
the author welcomes and appreciates links to and citations of his work. however, if you are viewing the full text of this article at any other website, be aware that its author does not endorse and is not compensated by any advertising or access fees you may be subjected to outside the original web and rss sites