Hopefully this article has shed some light on the basics and principles of why you should use stored procedures instead of regular SQL queries. If you're a database administrator, then stored procedures are a great way to hide complex programming logic from your developers. If you're a developer who isn't too proficient in SQL, then allowing your database administrator to create procedures that you can plug values into is a great way to get the data you need without the performance hit of an inexperienced user creating the TSQL code.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
SQL Server 
/ 149 
Extended Stored Procedures: Intro And 10 Cool Examples
