|
Vern Hamberg wrote:
Just spoke with a couple of the database guys at that "fictional"
IBM lab in Rochester - verified that the SELECT statement inside
the CREATE TABLE statement would be cached. I'd asked about
whether they could find a way to allow parameter markers in this
situation - said they could, but it is not in the standards.
Guess the answer to why it is this way is to read the SQL
standards documents - not IBM's - the industry-standard ones.
OK, now literals in the subquery can be parameterized in the plan
cache - so there would not be separate statements for each
separate literal value in a built-up statement string. There
might be different entries if the statistics on the column in
question show a skew for some values, resulting in a different
plan based on frequent values and histogram distribution and all
that.
So it isn't likely to be so bad as you suggest - there might be
hope, after all!!
Cool. Good to know.
If you are anywhere near the lab, then you are a /short/ walk from my not so fictional house ;-) I think I can see the stoplight at 41 St & 31 Ave, but I could for sure see some lights on the blue buildings when looking out my window just moments ago. You should stop over for a beer while in town :-)
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.