>-----Original Message-----
>From: Thomas Jeff [mailto:[EMAIL PROTECTED]]
>
>Rather a trivial question, but our DBA team is discussing how best
>to implement the location of the plan table. My preference is
>is simply create is as SYS, public synonym, and grant privs on
>it to our developers. I'm being outvoted by the others, who
>want to create it in each and every application schema, but still grant
>access to all developers with no synonyms, the thinking being, that
>it would help to minimize accidental deletions of execution plans
>and so forth.
>My belief is that's simply over-thinking this issue. What do you
>do at your sites?
How many developers share the same database? I've always created a common plan_table under a DBA account (but not under SYS) with a public synonym and access to public. Then I recommend to developpers that they use set autotrace or else put their name in the explain id, and I truncate the plan table about once a week. I haven't heard any complaints that execution plans were lost.
Actually, most developers don't seem to care much about execution plans anyway. :-)
