On 1/26/2012 11:21 AM, Stephen Russell wrote: > I don't live by mySQL like I do SQL Server so my experience is very limited. > > The base plan explanation that is a part of mySQL may not give all the > data that an add on by say Quest might do with say Toad for mySQL? > > Doing tests is the only way you find out here. The # of updates is > another factor as well as the sample size to the table containing the > transactions. > > In TSQL I have the include clause for an index. Is that available or > something like that in your mySQL version? I have better index > quality with include over a compound index.
I'm sure SQL Server and MySQL are similar in many respects. The links I posted earlier were helpful to understand how a compound index gets used as long as the fields referenced are in the same sequence. I just need to get into the habit of putting EXPLAIN before my SQLs to show me what to expect prior to the actual running of the SQL. -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
