Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 201-Table Variables

Posted on August 3, 2011July 30, 2011 by slowder

It’s been a while since I’ve added to my SQL 201 series, so I thought I’d pick up with table variables.  In an earlier post, I covered temp tables. Temp tables are a great place to dump in raw data, then transform it into another form so you can use it in a different way.  Table variables are similar.  You can dump in, transform it, and then pull it back out, all without having to worry about cleanup when you’re done.

There are a few questions I ask when determining when to use a table variable over a temp table:

  • Do you need the data to persist when you’re done with it?
  • Do you want to keep the data in memory?
  • You aren’t going to need an index are you?
  • You aren’t going to try to do an SELECT … INTO with the table, right?

As long as you don’t care about persisting the data, you want to keep the data in memory (and in theory as fast as possible) and you don’t want to index the data or SELECT data INTO the table, then I usually go for table variables.

So how do I define a table variable?

The syntax is somewhere between a table declaration and a variable declaration.

   1: DECLARE @<tableName> TABLE (

   2:     <columnName> <datatype>

   3:     , <columnName> <datatype>

   4:     ...

   5: )

You have to define the table variable name, then define the columns just like you would a normal table.  It’s really that easy.

Seems easy, what’s the catch?

Well, it’s not all sunshine.  There are some catches to using table variables.

  • You can’t truncate a table variable.  You have to start a new code segment and declare the new version of the table variable, or create a new table variable in order to change the columns in any way.
  • If you’re starting to use dynamic SQL, You aren’t going to be able to create the table in dynamic code, then have access to it outside the dynamic part of your query.  There’s a change of scope there.
  • SQL can’t generate statistics on a table variable, if you look at the estimated number of rows in an execution plan for a query that contains a table variable, you’ll see it estimates 1 row.  If you’re going to deal with tens of thousands of rows, table variables are not for you.  You need to consider indexing, which requires temp tables or regular tables.
  • If you need a nested stored procedure to reference the data in a table variable declared in the parent procedure, you’ll have to pass that variable to the child procedure.  Again, the scope changes when you enter the sub-procedure.

Conclusions

You have to understand the pros and cons for all three table types: real tables, temp tables, and table variables.  Each one has it’s use, and each one has cases where you can’t use them.  That’s why there are three.  Learning when you can and can’t use each of them is what you’ll have to learn to master SQL. 

When you come to a situation where you could use one or more of these tables, try two.  See which one performs better.  Testing and experimentation will teach you more than this article ever could.

If you have any questions, please send them in.  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