Naming Conventions For Sql Server Stored Procedures

SQL Server Naming Conventions and Standards Sql server, Sql, Learn sql

Naming Conventions For Sql Server Stored Procedures. I have seen various rules for naming stored procedures. In object explorer this prefix may well not be helpful in trying to find a stored.

This may causes some performance issues. Although it's probably not necessary, i prefix some object types: Uses stored procedures, defining a naming convention is absolutely critical for future supportability. Stored procedures named with the prefix sp_ are system sprocs stored in the master database. Typically the table name is referenced in the name, in the example above, the table would be useraccount. I personally will prefix my stored procedures with a unique name the describes what it does. 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. The stored procedure based on any qualifiers provided (database. There are only two hard things in computer science: From a usability point of view identifier names that begin with a number must always be quoted so.

If you give your sproc this prefix, sql server looks for them in the master database first, then the context database, thus unnecessarily wasting resources. Customer_getlist customerlist getcustomerlist getcustomers listcustomers. Standard naming convention for stored procedures or sp the standard naming convention for stored procedures are as follows: Some people prefix the sproc name with usp_, others with an abbreviation for the app name, and still others with an owner name. I don't like sp because too close to sp_ (system stored procedure). Sql server stored procedure naming styles. Stored procedures named with the prefix sp_ are system sprocs stored in the master database. As with tables and columns, i've seen many variations on procedure naming syntax. There are not a lot of the above and the prefix makes them easier to find in the source. 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. For tables and stored procedures, and most views, i use a prefix that indicates the business area of the object.