RE: SQL Delete Performance - Why so Horrible?

["Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>]

I think it is very likely that your deletes are doing full table scans
each time.  An index by company could make all the difference in the
world.  We had a situation here this week where an application was doing
some deletes and updates on an audit file based on keys.  Record
processing performance went from 3,500/records per hour to 10,000 per
minute just by adding the proper indexes.  

Jim

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of William Washington
III
Sent: Thursday, April 14, 2005 3:35 PM
To: midrange-l@xxxxxxxxxxxx
Subject: SQL Delete Performance - Why so Horrible?

Hi All,

Why is the SQL DELETE performace so terrible?

I have a file with 1,500,000 records.  When I do:

DELETE FROM filename WHERE company = pCompany

in a stored procedure running in batch, it takes nearly 30 minutes!  Of
course, an SQL DROP or a CL "CLRPFM" works within seconds, but I really
must check the company before deleting.

Would indexing by company help?

Thoughts?  Ideas?  Thanks.

William

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.