Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 103-Designing Stored Procedures

Posted on October 14, 2011October 17, 2011 by slowder

We’re nearing the end of the SQL103 series. We’ve designed tables, relationships, indexes and views. There’s plenty more to learn. Today we’re going to discuss designing stored procedures. When you start designing stored procedures you’re generally trying to build a wrapper around a collection of T-SQL statements that you can then hand off to developers. This wrapper buys you a couple things.

  • You make sure that everyone does the same action in the same way. Rather than allowing everyone direct access to update a table, you can build in extra logic to check the data being entered. Then everyone who tries to update the table will go through those checks since you only gave them access to execute the procedure, instead of direct access to the table.
  • Speaking of access, you can control who has the rights to complete a certain task.By only granting execute permission on a stored procedure, users won’t be able to directly update the table.
  • You can provide a layer of abstraction. Consider the stored procedure that let’s you update a table. You can make changes to the table, without having to make changes to anyone’s code. Since they just pass parameters to the stored procedure it won’t matter that you changed the name of the fname column to FirstName. It’s abstracted!
  • You have an additional layer of protection against SQL Injection Attacks. While switching from direct table access to stored procedures isn’t a cure-all for Injection Attacks, it’s a first step. If someone tries to inject select * from in as a parameter, and you’ve trapped your errors responsibly, the attacker won’t gain any insight into your system!

These are all good reasons for designing stored procedures. Now let’s dig into the design element.

So how do you design stored procedures?

Early in the design process you need to start asking, “how are you going to use this data?” You need to get an idea of how the end user is going to interact with it. Let’s consider our Customer table.

During the design process you should have asked that question.  Some of the answers you would have gotten back would have been: we want to be able to lookup customers by lastname.  We want to be able to update full names, we want to be able to update spouses.  Each of these three requests would start you down the path of developing stored procedures.

Since we already have a view for showing contact information, we might build the first stored procedure around the vContactCard view.  We would need to build a stored procedure that takes last name as a parameter, and returns the records as a result.  So we would have defined the following stored procedure.

USP_GetContactCardsWithLastName @LastName VARCHAR(50) — This stored procedure takes LastName, and returns all records from vContactCard where the LastName column equals the @LastName given.

We don’t have to actually build the stored procedure at this point, only define the inputs, the processing accomplished, and the outputs.

Think about the other two requests: updating names and updating spouses.  What definitions would you provide for these two requests?  Send in your suggestions in the comments, and we can discuss them further!  If you have any questions, send those in too!  I’m here to help.

 

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme