Naming Conventions For Sql Server Stored Procedures

SQL SERVER Location of Natively Compiled Stored Procedure and Naming

Naming Conventions For Sql Server Stored Procedures. Typically the table name is referenced in the name, in the example above, the table would be useraccount. Procclientbyconameselect, procclientbyclientidselect [4] lastly the action.

Some people prefix the sproc name with usp_, others with an abbreviation for the app name, and still others with an owner name. Standard naming convention for stored procedures or sp the standard naming convention for stored procedures are as follows: I have seen various rules for naming stored procedures. Show activity on this post. 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. Following a naming convention for tables, columns, and all other related database objects like views, stored procedures, indexes, triggers, etc., are important for the success and maintenance of a project. Both are important for teamwork. Never prefix your stored procedures with ‘sp_’. By following a naming convention, you can spend less. Although it's probably not necessary, i prefix some object types:

Both are important for teamwork. You shouldn't use sp_ in sql server unless you really mean it. Show activity on this post. You could have, among other things, these choices: There are no technical issues with this. Sql server stored procedure naming styles. Some people prefix the sproc name with usp_, others with an abbreviation for the app name, and still others with an owner name. Works with any relational db in a smart way. There are not a lot of the above and the prefix makes them easier to find in the source. Sql server always looks for a stored procedure beginning with sp_ in this order: 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.