I'm sure there are differing opinions on this, but I've heard several SQL Server gurus suggest that you not use sp for your stored procs. They said that instead of thinking sp means "stored procedure" think of it as "system procedure", meaning they're procs that ship with SQL Server. This actually makes sense. In newer versions of SSMS, these procs are stored under "System Stored Procedures"
>I am sure this question has been asked a million times. And yet I am asking it again. I see everywhere online stored procedures named with prefix sp (e.g. sp_custom_account). Is there a technical or a logical reason for that? Since stored procedures are in SQL DB Programmability -> Stored Procedures, why need to tag them as SP still?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer