SQL Delete Performance - Why so Horrible? -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: SQL Delete Performance - Why so Horrible?
From: William Washington III <w.washington3@xxxxxxxxxxxxx>
Date: Thu, 14 Apr 2005 13:34:50 -0700 (PDT)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

Follow-Ups:

RE: SQL Delete Performance - Why so Horrible? , Elvis Budimlic
RE: SQL Delete Performance - Why so Horrible? , Elvis Budimlic
Re: SQL Delete Performance - Why so Horrible? , MWalter

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.