RE: Primary Keys optional?

Wierd! I was just having a PK-vs-UniNN discussion with a co-worker. Our current ERP (which shall remain nameless) also doesn't use PKs. At some point on 8.1.7 or 9.2.0.5, we had a poorly performing query (go figure). One of the tables involved had a segmented unique key whose member columns also each had a NN constraint. Converting this to a segmented PK gave me a different explain plan. As I recall, it was better, but it's been awhile.  

Has anyone else ever seen this? There's no way I could hope to have the time to reproduce it now... :( And I may have already drowned the brain cells responsible for the majority of that particular memory, so there's that caveat.  

Rich    

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jared Still Sent: Friday, August 18, 2006 11:29 AM
To: Brandon.Allen_at_oneneck.com
Cc: andert_at_gmail.com; oracle-l_at_freelists.org Subject: Re: Primary Keys optional?

[snip]
 

SAP is similar. They do not use RI nor PK. They do have unique indexes with NOT NULL columns, so PK can be created if necessary. (Think replication)

[snip]

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist 



--
http://www.freelists.org/webpage/oracle-l