Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

Code to Write Code

Posted on January 16, 2009May 10, 2011 by slowder

I’ve read “When you start writing code that writes code for you, you’ve moved up from a beginner to a professional.” Today I’d like to walk you through an example of where learning to write this kind of code pays off.

At my we have a table that defines a hierarchy. Each level on the hierarchy has a description. Here’s a very generic example:

1. chapter
	1.1 heading
		1.1.1 sub-heading
			1.1.1.1 detail one
			1.1.1.2 detail two

We have a stored procedure that will let you pass in 1.1.1.2 and get all the descriptions down to that level, so the “full description” of 1.1.1.2 would be:

1. chapter
	1.1 heading
		1.1.1 sub-heading
			1.1.1.2 detail two

After a while we determined that building this description on the fly was too expensive in terms of time. We decided to build a column to store this long description, eventually we would make this column a computed column and the long description would update whenever a change was made to the record.

Before we could make that change, we had to compute all the long descriptions and store them in the column. Rather than executing hundreds of thousands of stored procedures I built a query that created the execute statement for me, and let that take care of this process.

For the purpose of this demo, we’re not going to get into how the stored procedure builds the hierarchy, then stores it. We’re just going to assume it does that part. We pass in the ID for the record, and it fills in the long description for us.

First get a list of the records you need to process.

SELECT ID
FROM workingTable
WHERE
	LongDescription IS NULL

That list of IDs will form the basis of our WHILE loop. For each one of those, we’re going to run the stored procedure.

WHILE EXISTS ( SELECT ID
	FROM workingTable
	WHERE
		LongDescription IS NULL)
BEGIN

END

With this WHILE loop, we can do something for each ID found. Be careful you remove records from that list in the body of the loop, or you’ll never exit the loop. We’ll take care of that, by adding our EXECUTE step. To do the EXECUTE step, we need to set up a variable to hold the ID for processing.

DECLARE @ID INT

WHILE EXISTS ( SELECT ID
	FROM workingTable
	WHERE
		LongDescription IS NULL)
BEGIN
	SELECT TOP 1
		@ID = ID
	FROM workingTable
	WHERE
		LongDescription IS NULL

END

At this point, we can’t run this code since we’d never leave the loop, but with one more step, we can actually process each ID, which updates Long Description and removes it from the results returned in the EXISTS check.

DECLARE @ID INT

WHILE EXISTS ( SELECT ID
	FROM workingTable
	WHERE
		LongDescription IS NULL)
BEGIN
	SELECT TOP 1
		@ID = ID
	FROM workingTable
	WHERE
		LongDescription IS NULL

	EXEC usp_storeLongDescription @ID
END

Now each time it hits this loop, it will create the long description, then update the LongDescription field, changing it from NULL to a defined value.

This makes the process far easier, than writing several thousand EXEC usp_storeLongDescription statements!

If you have any questions about this process, please let me know. 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