Ordering data using dynamic SQL versus temporary tables
Here’s a scenario that’s not that uncommon:
You have a query and the user wants to be able to choose at run-time which column to sort/group by.
The problem is you can’t use a variable to indicate the column name in the ORDER BY or GROUP BY clauses.
If the query itself is very simple, then you could just repeat the query with specified ordering using IF. eg.
IF (@order = ‘Column1’)
SELECT * from Table1 ORDER BY Column1
ELSE IF (@order = ‘Column2’)
SELECT * from Table1 ORDER BY Column2
If the query is non-trivial, you probably wouldn’t want to use this however, as maintenance becomes problematic.
There are two obvious solutions to this:
Dynamic SQL
Assemble the query into a varchar variable and then execute it using sp_executesql.
DECLARE @sql varchar(4000)
SET @sql = ‘SELECT * FROM Table1’
IF (@order = ‘Column1’)
SET @sql = @sql + ' ORDER BY Column1'
ELSE IF (@order = ‘Column2’)
SET @sql = @sql + ' ORDER BY Column2'
sp_executesql @sql
Temporary Tables
Split the query into two parts. First of all, retrieve the data into a temporary table (this is one of the few times you can’t use a table variable). Next, use the original IF .. ELSE IF method to return the data from the temporary table.
SELECT * INTO #Stuff FROM Table1
IF (@order = ‘Column1’)
SELECT \* FROM #Stuff ORDER BY Column1
ELSE IF (@order = ‘Column2’)
SELECT \* FROM #Stuff ORDER BY Column2
So which is better? Great question, and I’m not really sure of the answer. I suspect it could well be “it depends”.
Categories: SQL