Naming Conventions For Sql Server Stored Procedures

Microsoft SQL Server security best practices checklist

Naming Conventions For Sql Server Stored Procedures. That the standard makes sense. All internal sql server stored procedures are prefixed with sp_, and it is recommended not to prefix stored procedures with this as it is a little slower.

There are not a lot of the above and the prefix makes them easier to find in the source. Both are important for teamwork. However, i think i could have spent a little more time on naming conventions for stored procedures specifically, since this is an issue i've seen countless times in my career, and have seen several times since my earlier post. You shouldn't use sp_ in sql server unless you really mean it. For tables and stored procedures, and most views, i use a prefix that indicates the business area of the object. I have seen various rules for naming stored procedures. To me it just makes it easier to read and decipher what the sql server stored procedure is used for. By following a naming convention, you can spend less. Ad smart autocompletion for sql, code inspections, database navigation. As with tables and columns, i've seen many variations on procedure naming syntax.

Sql naming conventions are one of these. Although it's probably not necessary, i prefix some object types: From a usability point of view identifier names that begin with a number must always be quoted so. The stored procedure in the master database. Works with any relational db in a smart way. Never prefix your stored procedures with ‘sp_’. As with tables and columns, i've seen many variations on procedure naming syntax. Consider a stored procedure to get the list of customers. For example, you can use the dynamic sql to create a stored procedure that queries data against a table whose name is not known until runtime. That the standard makes sense. It isn't going to make any difference to sql server.