× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2005

RE: SQL Delete Performance - Why so Horrible?

I forgot to ask, how many indexes already exist over this physical file?  If
there are many, they need to be maintained during the delete.

-----Original Message-----
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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.