(Pete Cresswell) wrote:
>RE/
>
>
>>Sounds like you've not understood what global temporary tables are about?
>>
>>
>
>I think you've nailed it.
>
>I was missing the "fixed structure, data-visible-to-only-inserting-session"
>part.
>
>Now it makes more sense.
>
>I'm taking the "no schema changes except under controlled cirumstances" part on
>faith. Would the prohibition be because letting somebody do a CEATE
>TABLE/DROP TABLE for temp tables mean that they could do the same thing with
>"real" tables?
>-----------------------
>PeteCresswell
>
>
The reasons are as follows:
- Kills performance and scalability
- The privileges to create objects do not belong in a production schema
except during brief periods when it is being built or modified
under the direct supervision of the DBA.
- Completely unncessary so no reason to do it.
--
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)
Received on Mon Sep 22 2003 - 19:20:07 CDT
