Abu Dina (11/18/2013)
Ah! Then you need to be introduced to the INTO Clause 😉
A couple of caveats to using this technique:
- All columns created will default to allow NULL values.
- You may want to try to control the length of any VARCHAR columns that get created in the output table.
- The temp table will have no PRIMARY KEY, but you can add one after setting the participating columns to NOT NULL.
- No constraints (FK, default, etc.) will get inherited by the temp table.
Otherwise, I agree it is quite useful.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St