Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: Enterprise
Expertise: Intermediate
Dec 19, 2000



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Be Careful How You Name SQL Server Stored Procedures

When creating stored procedures in a database other then the Master database, avoid using the 'sp_' prefix. System stored procedures are the only ones that should use the 'sp_' prefix. The issue is not that naming a procedure in this manner causes errors executing the procedure, but rather it slows down execution. When a procedure is named 'sp_', SQL server first looks in the Master database to resolve where the procedure is located. If it is not in the Master database, execution time is wasted attempting to look it up. SQL Server then looks up the stored procedure name as if the object owner is 'dbo'. If the procedure is in the current working database, then it is executed.
Andrew Holliday
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date