Thank you for the responses ---- we've been spoiled by using sybase SQL Anywhere in that the entire database is stored in one file. I'm worried about having our service people, many of whom are in asia and for whom english is a second language, suddenly having to deal with about 300 files for the database after being used to just dealing with one file. (We have about 100 tables total, though only one is huge).
Have you seen this to be an issue? If I use MyISAM tables, will MySQL give descriptive messages if someone accidentally deletes or moves just one of the files? Will our field engineers/service people have to become 'mySQL DBA's' to manage and maintain our customers' databases? (That would be a bummer and involve a lot of training in some areas) Thanks! holly -----Original Message----- From: Pete McNeil [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2003 4:17 PM To: Holly Chamberlain Subject: Re: What do you recommend: MyISAM or INNODB? No question. MyISAM. _M At 02:01 PM 10/10/2003, you wrote: >Hi Group, >I'm requesting feedback - should I use MyISAM or Innodb tables, or a >mix? My database (currently in Sybase) typically gets no larger than 50 >gigs, but 99% of the data is in one table. > >(The app is an cleanroom monitoring system, we collect 3-5,000 records a >minute from environmental sensors that are installed in cleanrooms.) The >data in this big table is never updated, and very, very rarely deleted. >We just add it and later users select it to display parts of it. What we >need most are fast queries and fast inserts. > >What would be better for performance and maintenance- all MyISAM tables? >INNODB tables? Or a mix? > >Thanks! >Holly > > >-- >MySQL General Mailing List >For list archives: http://lists.mysql.com/mysql >To >unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
