primary/ foreign key constraints for oltp, overhead?

From: Amar Kumar Padhi <TS2017_at_emirates.com>
Date: Fri, 08 Jun 2001 21:01:11 -0700
Message-ID: <F001.003230E2.20010608205019@fatcity.com>

Hi,
my current project database has no primary/ foreign key constraints. Curious about this basic check missing in the system, I was informed that these constraints result in lot of locking issues and would be a bottleneck to huge OLTP Systems.

As per my knowledge, locking of master as well as detail would only occur if one is trying to delete a master record the corresponding details records exists. In this case both master and detail records are locked (on delete cascade option).

Has anyone come across such issues in huge dbs, where using these constraints actually resulted in performance issues?

rgds
amar
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Amar Kumar Padhi
INET: TS2017_at_emirates.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Fri Jun 08 2001 - 23:01:11 CDT