Re: atrocious update performance

while you weren't looking, Kevin Barnard wrote:

> Have you added indexes for the custid column for tables
> account.acct accunt.orgacct and note?

They were indexed in the original case, yes. There was no
need to index them in today's test case, as that was done
purely in attempt to rule in or out foreign key validation
as the cause of the performance hit. No foreign keys that
might be validated, no need to index the foreign key columns.

> I haven't followed the entire thread but it you have
> cascading FK on those tables without an index on the
> column that could cause your delay.

The issue is that the foreign keys are being validated at
all, when the column being referenced by those foreign keys
(account.cust.custid) is never touched.

Regardless of whether or not the referencing columns are
indexed, validating them at all--in this specific case--is
broken. The column they refer to is never touched; they
should remain utterly ignorant of whatever happens to other
columns in the same row.

/rls

--
Rosser Schwarz
Total Card, Inc.