|
I think indexing by company would help. Or roll your own delete using some HLL. BTW, do you have a lot of deleted records in this file already? SQL looks at the deleted records as well. Is there a CASCADE constraint defined on the delete? This may be adding to the processing time. Elvis -----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 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.