|
|
Posted by DA Morgan on 09/08/06 01:03
Erland Sommarskog wrote:
> (cphite@gmail.com) writes:
>> There are a lot of reasons someone might want to create a table on the
>> fly. They might want to store a snapshot of data at a given time that
>> is easily accessable. It may not fit your ideal of how SQL "should" be
>> used, but it's actually quite common in the real world - and it need
>> not invoke images of falling pachyderms.
>
> Yes, temp tables are a fair game, but dynamically named tables isn't.
> If nothing else, because it's completely painful to work with them.
Following this from an Oracle perspective I am horrified at the use
of these create-a-table on-the-fly methodologies and was hoping that
the changes in SQL Server 2005 would render them a thing of the past.
One question about them though ... how does the optimizer deal with
them?
Thanks.
--
Daniel Morgan
University of Washington
Navigation:
[Reply to this message]
|