|
Of the 1.5 million about how many records are you removing? If it is a small % then indexing by company could help dramatically (or at least it would with a select, I have never had a performance sensitive delete). -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of William Washington III Sent: Thursday, April 14, 2005 4: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.
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.