Re: massive MySQL tables

I have similar problems with 2 huge forms. The best thing I am doing is to divide among lots of Mysql tables. And follow a lot of performance hints from its manual. For example, separate variable length fields from those who are not (ie Varchar in a table, Int on another). And so it goes... Maybe if you are really concerned, store some data that will never change in files.... Non-dynamic data doesn't follow the database concept, does it?... :-) -- Julio Nobrega A hora está chegando: http://toca.sourceforge.net "Justin French" <justin@indent.com.au> wrote in message news:3BC22718.CF31EF78@indent.com.au... > Hi all, > > Sorry for being slightly OT, but I'm working on a site with a large > application form (84 fields) which people have to fill in. The form is > rendering in the browser pretty quick (my first worry), but now I'm > concerned that 85+ data fields in MySQL might create performance > problems on the server. > > Is this likely? > > Most fields are "medium text" or "varchar", and will not need to be > searched at all, so i'll prolly just index the two or three important > ones, and leave it at that. > > > If there is likley to be a performance hit, what other options will I have? > > > Justin French