I am in agreement with the "gurus" and thinking of changing my stored procedure names to be more consistent and logical. My SQL Server is used by both VFP 9 application and ASP.NET C# application. So I will start naming the stored procedures with the prefix indicating where they are used. E.g.
web_blablaba - used by ASP.NET
vfp_blablabla - use by VFP
>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?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
