Hello Roger,
[snip] > > Roger, I attempted adding additional space with a new file under > > innodb_data_file_path as follows; > > Before: innodb_data_file_path = ibdata1:50M;ibdata2:50M > > After : innodb_data_file_path = ibdata1:50M;ibdata2:50M;ibdata3:50M > > Stopped and restarted MySQL, but this did nothing. Could you > please point > > me! > > I have no idea, try <URL: http://www.mysql.com/doc/I/n/InnoDB.html > > > Maybe someone on the list who have actually used the inndb tables > could give > you a hint...? I got this to work, I suspect a typo resulted that it did not work the first time. It was a matter of adding the extra ibdata file (as above), stop/start, and viola, space was added. [snip-1] > > This is also my understanding. It scares me. Thus when using > MySQL with > > InnoDB, all data of all databases on my different website stages, viz., > > PROD, QA, DEV would share the same InnoDB dataspace for data. > > yes, but this is not so bad, is it...? [snip-2] > > Thus PROD data is at risk. > > why? [snip-3] > > And furthermore, data cannot be backed up separately. > > Yes, it can, the mysqldump utility will address the _database_, > but you can > not do backups of individual databases by simply copying the > files on the OS > level, like you can with myisam tables. [snip-4] > What exactly do you see as a risk? Well, i.r.o. the matter of risk, if different websites's data is in one set of files, and especially with DEV, where programs which still have bugs or with finger trouble, could damage the data in general for PROD system; also they would interfere with PROD throughput & etc. I have an extremely good backup program which I would stick to; now it'll be fine with different databases each at a separate location. At some point, I'll also look at mysqldump, thank you. NB. In the meantime, I also posted this issue to InnoDB's Heikki Tuuri, who confirmed my concerns - but only if used in one MySQL server instance; he advised the actual way to handle this, is to run separate MySQL server instances. I'm busy setting this up. With different instances, each instance could have its dedicated datadir & etc. I use Win2k Pro; struggling with multiple instances; MySQL does not see the /mysql/data/my.cnf - for some reason it only sees c:/winnt/my.ini and c:/my.cnf. I started another thread, 'Multiples instances of MySQL' asking for assistance. BTW, Heikki's response; >[snip] >> It is better to run a different instance altogether of mysqld for >> production >> and development systems. Development will inevitably cause >> disturbance to a >> production system. The same with co-hosting: high load on one >> database will >> make others freeze. [snip-1] > It is not a very big difference between one 'tablespace' (or multiple, > possibly spanning multiple disks) sharing multiple databases, and one (or > more) disks with separate databases in separate files. The database > partition can be seen as a kind of filesystem... [snip-2] > It is an issue, but I don't think it is a big issue. Sorted with finesse with multiple instances. Anyway, Roger thank you for all your assistance. And BTW, the more I work with MySQL, the more I'm enjoying it. Kind regards Emmanuel --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
