Hi Neil, Many times we need to generate reports (weekly, montly, yearly) from the data we have. For detailed reports we have to use joins on many tables. So, it takes time from 2 to 5. So these types of activities must be performed on slave server.
If you need reports then you should have master - slave replication. http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html _Krishna On Thu, Mar 18, 2010 at 3:11 PM, Tompkins Neil <neil.tompk...@googlemail.com > wrote: > Hi > > How do you mean "executed on slave" ? > > Neil > > > On Thu, Mar 18, 2010 at 9:32 AM, Krishna Chandra Prajapati < > prajapat...@gmail.com> wrote: > >> Hi Neil, >> >> Recommend : Innodb storage engine >> >> Even, i would suggest inner join select query (if report query might takes >> few seconds) should be executed on slave. >> >> Before doing any thing. Plan out all the requirement. >> >> Regards, >> Krishna >> >> >> On Thu, Mar 18, 2010 at 2:48 PM, Tompkins Neil < >> neil.tompk...@googlemail.com> wrote: >> >>> Hi >>> >>> I'm currently looking to develop an on line web application - which is >>> going >>> to be used by around 200+ concurrent users at any one time. Can >>> you recommend to me the best/preferred MySQL database engine to use for >>> example MyISAM ? >>> >>> Also, in your experiences, do you recommend that SELECT statements >>> containing a number of INNER JOINS should be execute from a Stored >>> procedure >>> or purely from the webpage ? >>> >>> Cheers >>> Neil >>> >> >> >
