A table of sequence numbers is often involved in a CROSS JOIN with a table of working data. The result set contains a row for every combination of working data and sequence number. This method can be used to replicate the rows of the working data. All rows are replicated N times by default, but a WHERE clause can selectively replicate specific rows in different quantities. For example, if table Address contains addresses for mailing labels the following query would produce three labels for addresses in Nebraska/Kansas/Oklahoma and six labels for all other addresses.
SELECT * FROM Address CROSS JOIN dbo.udfGetSequence(1,6) WHERE Number < CASE State WHEN 'NE' THEN 4 WHEN 'KS' THEN 4 WHEN 'OK' THEN 4 ELSE 7 END
Here's another way to get the same result.
SELECT * FROM Address, dbo.udfGetSequence(1,6) WHERE State NOT IN ('NE','KS','OK') OR Number < 4
A table of sequence numbers can also be used as an index into a string value to provide a set-based approach to some common string manipulations. Listing 2 is a user-defined function that counts the number of times one string is found within another string. Listing 3 is a user-defined function that parses a delimited string into individual elements. Both of these functions use the earlier function to generate a table of sequence numbers. Here are some example uses of the two functions.
DECLARE @S varchar(2000) SET @S = 'football basketball baseball hockey soccer volleyball golf tennis' SELECT dbo.udfCountString(@S,'ball') This returns the value 4. DECLARE @S varchar(2000) SET @S = 'This fine line is a baseline for the incline of the main line.' SELECT dbo.udfCountString(@S,'[ ]line[;,.!? ]') This returns the value 2. DECLARE @S varchar(2000) SET @S = '1,12,123,1234,ABCD,ABC,AB,A,*' SELECT * FROM dbo.udfParseString(@S,',') This returns a table of nine rows with each one containing an index, an offset, and a string. 1 1 1 2 3 12 3 6 123 4 10 1234 5 15 ABCD 6 20 ABC 7 24 AB 8 27 A 9 29 *
I hope these functions are useful for you and/or help you come up with creative ways to use a table of sequence numbers.
Editor's Note: If you would like to receive similar tips on SQL Server administration and development, be sure to subscribe to the SQL Server Adviser newsletter. Sign up now!
Brian Walker is a Senior Database Architect in an IS department that uses SQL Server 2000 and the .NET Framework. He has over 25 years of experience in the IT industry with the last several years focused on databases and SQL Server. Brian is a software developer, database developer, database administrator, and database consultant. He develops utility software as a hobby, including a large collection of SQL Server utilities.
This was first published in April 2005