All, I cam remember a conversation with a PeopleSoft Apps developer on this subject. He stated that "The App is much more efficient at maintaining the foreign key referential integrity and business logic than the database.". That held a touch of water until the 'app' fouled up and we ended up with a Bill of Materials that had no product it was used for. At that point we discovered that the real reason for no referential integrity is that they do things in reverse so that the RI would get in the way. Programming dilemma fixed by crippling the DB. Dick Goulet Senior Oracle DBA ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Peter Robson Sent: Sunday, January 23, 2011 10:32 AM To: jkstill@xxxxxxxxx Cc: info@xxxxxxxxxxxxxxx; niall.litchfield@xxxxxxxxx; ORACLE-L Subject: Re: interesting snippet from Oracle FUD paper And people pay money for these software cludges?! It has always astonished me that companies like Oracle can market themselves as Relational DBMS vendors, and then produce products which drive a horse and cart through the very theoretical standards they are supposedly espousing. Still, I guess it keeps the consultants off the streets! <Sorry David... :-) > peter On Fri, Jan 21, 2011 at 2:09 PM, Jared Still <jkstill@xxxxxxxxx> wrote: On Thu, Jan 20, 2011 at 8:38 AM, Go-Faster Consultancy Ltd. <info@xxxxxxxxxxxxxxx> wrote: There are no primary key indexes in PeopleSoft - they only unique indexes. Neither is there any database enforced RI. Same goes for SAP - there are 0 foreign keys in an SAP database, at least in my experience. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com