Re: PeopleSoft SQR Development Question

["Hope, Sandra" <HopeS@DYNCORP.COM>]

Sandra Hope
DynCorp
hopes@dyncorp.com
Office:   (703) 715-4428
RESYSTEMIZATION
PeopleSoft

> ----------
> From:         Mike Fulce[SMTP:m.fulce@USM.EDU]
> Reply To:     SQR-USERS@USA.NET
> Sent:         Friday, October 02, 1998 4:32 PM
> To:   Multiple recipients of list SQR-USERS
> Subject:      PeopleSoft SQR Development Question
>
> Maybe this is more for DBA's (specifically ORACLE) than developers.
> (However, I'm not looking for philosophy, just practicality)
           I'm a developer not a DBA!
> I'd just like to hear how some of your shops manage the SQR development
> environment with PeopleSoft, ie:
>
> Do you allow developer's to run SQR's outside of PeopleSoft as user
> sysadm?
        Typically, developers are (should be) allowed to run SQR's outside
of PS since this allows more flexibility.

> If not, then how do you handle table reference coding in SQR's? Do you
> create synonymns for all of the PS tables or do you force the developers
> to
> code the schema name?
>
> What privileges do you give your developer's in the development database?
> Full or limited? If limited, please specify.
        Some companies allow full access and sometimes get into trouble if
the developers aren't sure of what they are doing; other companies provide
minimal to all and then piece-meal additional access to others as-needed.

> Do you allow custom SQR's to build/drop temporary tables dynamically or do
> they use truncate on existing tables that the DBA created.
        If build/drops occur on a regular basis, the database will become
fragmented and cumbersome.  Truncate allows data to be dropped but
tablespace to remain.

> I would like to have a loose development environment by giving SQR
> developers privileges to be able to connect to the development database
> outside of PeopleSoft to do queries or to run SQR's directly and to be
> able
> to do some DDL. However, since we are new to PeopleSoft and Oracle/SQR,
> our developer's are inexperienced. So I really don't want them connecting
> with the privileges of user sysadm outside of PeopleSoft.
>
        If your developers are inexperienced, limit their access; they can
        unknowingly create problems.  You can limit access to specific
tables
        (not sure if this applies to commands like 'delete').

> I'd appreciate any responses.
> __________________________________________________________________________
> ____
> Mike Fulce                    __   Oracle Database Administrator I
> OTR-Admin. Resources      ___/ /__ University of Southern Mississippi
> m.fulce@usm.edu          /__  ___/ Voice:(601) 266-6102 Fax:(601) 266-6881
> 207 Forrest County Hall    / /     Box 5171, Hattiesburg, MS 39406
>                           / /      http://ocean.otr.usm.edu/~rmfulce
>                           ^^
>