If the table has 60 rows, then any plan and any query will do. I was talking about one 61th of rows, not a single row in the whole of total 61 rows. If the table needs to be periodically cleared of old rows, it probably grows quicker than one row a day.

Clustered indexes do have something to do with the thing. If you use a non-clustered index, then the index basically only contains references to the rows. Therefore for the index to be beneficial to the query execution, the number of selected rows has to be smaller compared to the total number of rows, than for a clustered index. Though with a delete it's probably a little different at least with MSSQL because deleting a whole range of rows means a fairly big change to the tree ad if the table is wide enough ...

I just tested it on MSSQL with a 600 row table (fairly wide) and could not get it to stop using even the nonclustered index even when the condition was expected to select 98% rows. Not even with a 10000 rows table (same width, the table was created by a SELECT TOP xxx FROM a real table).

I guess whoever ends up doing the actual job will need to test it out and find out what works best in this particular situation. In either case I would recommend writing queries so that the server may decide to use an index. No matter whether the index exists at the moment or not. Unless of course it means you have to bend backwards to write it like that.

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re^6: CGI Program To Delete Old Data From MySQL Table? by Jenda
in thread CGI Program To Delete Old Data From MySQL Table? by Milti

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.