Why it is not a good idea to name your stored procedures sp_…
February 2nd, 2006
No comments
Recently I was reviewing an internal database developent project which was expected to be released soon. While the overall code quality was good, one thing caught my eye: developers had named all stored procedures according to the sp_… scheme. What’s wrong with it? Even Microsoft SQL Server Devs are using this convention. Well, that is actually the catch.
While SPs with this prefix are executing correctly, they are causing an increased lookup time when called. This is due to the fact that all procedures starting with sp_ will be resolved in the master DB first, and only if not found there in the current database.