Re: create any table in schema

Generally speaking the 'best practice' is for developers to send all objects to a designated senior developer or development DBA to build them. The reason is not just a matter of permissions. The reason is that running it all thorugh one person gives the ability to validate spellings, to validate naming conventions, to make sure that constraints are appropriate and all foreign keys do what they are supposed to do.

Daniel Morgan

Matthew Hallam wrote:

> "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<1019148032.14139.1.nnrp-14.9e984b29_at_news.demon.co.uk>...
>
> > You could create a procedure owned
> > by the schema where the table is to be created,
> > executable by the schema which is to create
> > the table.
>
> cheers, I just wondered if there was any obvious "grant" command i'd missed,
> sadly it looks like not then!
>
> > It's not particularly good practice though to have
> > production systems creating (and dropping)
> > objects on the fly
>
> indeed, this is for development only - to allow the developers to logon as
> themselves but create objects in a common schema to build the final end system.
>
> "Daniel Morgan" writes :
>
> > Does this relate, in any way, to creating temp tables?
>
> nope :)
>
> thanks,
> Matt
Received on Fri Apr 19 2002 - 10:32:14 CDT