Thanks for the response Billy. > That shouldn't be a problem. Either your database has gotten > huge, or they don't know how to manage their DB. (or have > overloaded their servers; common with shared hosting)
Probably first and last. The query is simple, but two tables joined, and one is 500,000 records - and is joined on a field it is not indexed on. In that table, there are 6 different fields that are commonly parsed by/joined on, and the one in question is at the bottom of that list. I worry if I index it, I will solve the problem for those two pages yet create one with the rest of the site, by slowing down operation on everything else. I'm only asking for 12 records in this query but the db time is extreme. Question: if I made a VIEW that was composed of four tables, would the processing speed of the view have the same limits that doing the view-create- query would if I ran it prior to (or as part of) what I was doing "with" the view? I'm thinking maybe I could make a view that would combine some data so my in-page queries were much simpler - but if it's merely moving the combine query from the page to the table I'm not sure how much that would help. Regards, Palyne ------------------------------------------------------------------------- This email server is running an evaluation copy of the MailShield anti- spam software. Please contact your email administrator if you have any questions about this message. MailShield product info: www.mailshield.com ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org
