Re: PeopleSoft SQR Development Question

[Michael Lee <MLee@AGCONSULT.COM>]

Mike,
These are very good questions.  However, the PS-Users mailing list may be a
better place to discuss this (You can subscribe at
http://www.ps-users.com).  I say that because lately, this list has been
flooded with lots of mail.  Anyways, everyone pretty much has a different
methodology when it comes to DB access by developers.  So, I must announce
that this is just my opinion.

In general, the developers should have loose access when it comes to DB
security, Tools access, etc.  Having a version control/source control
system also helps out in the development environment.

If you have a tight, monitored development area, you will be pushing more
responsibility to your PeopleSoft Security Admin as well as the DBA(s).

In my opinion, when the development area is NOT a "loose" environment, then
the project tends to go very slow because you will have to funnel your
requests through to the proper people.

Your system integration/user acceptance TEST database should be a locked
environment.  And, your production environment should of course be locked.
You may want your tech lead and your PeopleSoft security administrator to
have tools/SQR (outside of PS)/sysadm access.  All other developers should
have full access to the development area.

The demo database is usually open to all.  I would suggest refreshing this
every 2 weeks or every month.  Make sure that when you have a minor
upgrade, to refresh the database, then perform the upgrade, and then back
up the database again...  i.e. when going from 6.00 to 6.01, refresh the DB
with 6.00, then upgrade to 6.01, then backup the 6.01 database.  PeopleSoft
doesn't ship a demo DB for minor upgrade releases, and you want to have a
clean DB when upgrading the demo database.

If you have any other questions, feel free to contact me at my client site
(M-Th):  312.653.5026.

Michael K. Lee
mlee@agconsult.com
Consultant
AG Consulting, an ADP Company
http://www.agconsult.com






Mike Fulce <m.fulce@USM.EDU> on 10/02/98 01:32:23 PM

Please respond to SQR-USERS@USA.NET

To:   Multiple recipients of list SQR-USERS <SQR-USERS@list.iex.net>
cc:    (bcc: Michael Lee/Application Group)
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'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?

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.

Do you allow custom SQR's to build/drop temporary tables dynamically or do
they use truncate on existing tables that the DBA created.

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.

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
                          ^^