RE: setting up two instances of mySQL
Hi Chris, I am Tom, you know your manager, did you say that I am wrong!!! Just kidding :-). Well I cannot find any good reason for having two databases in two different instance. Do you have two Oracles or Microsoft SQL Server instances in the computer? Nope. The only reason when that is acceptable, is when you want to keep two version of the same database engine. Like having 3.23 and 4.0. Having two MySQL instances is going to complicate things making everything more difficult to maintain and install. Good Luck. --- Cal Evans [EMAIL PROTECTED] wrote: The pros are you can run them under separate user/group ids therefore you can make it much harder for someone with access to only one to get to the other's data. The cons are that you will have 2 copies running therefore it will take longer to maintain. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -Original Message- From: Chris Stefanick [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 7:56 AM To: MySQL Support Subject: setting up two instances of mySQL I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? Thanks so much, CS - 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 - 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 __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com - 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
Re: setting up two instances of mySQL
Hi, I don't want to get in the way, but I am experiencing similar issues. Here's the problem I'm trying to find a resolution to: We have one instance of MySQL (it was configured and installed once). This instance has one 'test' 'database', and one 'mysql' 'database'. The mysql database contains the grant tables. I want to create a few other 'databases'. One should be used for keeping recipies, for instance, and the other will contain the data I use for the electronic key card system I use in my house (for instance). Both databases run under the same 'instance'. The recipe database is updated frequently, because I am active in a cook's collective and we routinely update each other's recipies as we develop more refined ways of making the dishes. The key card database is not updated frequently, but is heavily accessed by several custom-made hardware devices. One day, a bug in the network protocol I use to connect the card swipe device to the database causes some of the data in the database to become corrupted in the key card database. This happens as I get home late at night after bar hopping, and I don't discover it until noon. The corruption involves data that was deleted, so I need to restore that database to just before midnight, using the full backup I wisely took at 8PM before going out to the bars, in conjunction with the update log which I have on a RAID5 device for protection. The problem is, that if I restore the database from the last cold backup, then apply the update log until midnight, I will lose all transactions that occurred against the recipe database between midnight and noon the next day! Oracle and SQL Server allow you to restore databases independently of one another. I cannot discern the method to do so in MySQL. Surely this is a common requirement? Is there an easy answer I have overlooked during my evaluation of the restore options? By the way, the above scenario assumes MyISAM table types. I understand from other postings that InnoDB can restrict the options even further. The obvious solution seems to be separate MySQL 'instances' for each database you want, so that the transaction logs are kept distinct from one another. If this is the preferred solution, I would be interested to hear how some production environments have been set up. Thanks! Josh Horton Francisco Reinaldo wrote: Hi Chris, I am Tom, you know your manager, did you say that I am wrong!!! Just kidding :-). Well I cannot find any good reason for having two databases in two different instance. Do you have two Oracles or Microsoft SQL Server instances in the computer? Nope. The only reason when that is acceptable, is when you want to keep two version of the same database engine. Like having 3.23 and 4.0. Having two MySQL instances is going to complicate things making everything more difficult to maintain and install. Good Luck. --- Cal Evans [EMAIL PROTECTED] wrote: The pros are you can run them under separate user/group ids therefore you can make it much harder for someone with access to only one to get to the other's data. The cons are that you will have 2 copies running therefore it will take longer to maintain. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -Original Message- From: Chris Stefanick [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 7:56 AM To: MySQL Support Subject: setting up two instances of mySQL I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? Thanks so much, CS - 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 - 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 __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA
RE: setting up two instances of mySQL
As Cal stated, there is actually a very important reason. MySQL is lacking in fine-grained security. I can give a user the ability to add databases. But can I give that user the ability to only drop databases he/she created? I sure haven't found any documented method. So, if you're in a large organization, and you don't have a certain level of trust between the groups within that organization, each group will need it's own instance of MySQL. Those instances could be on sererate physical machines (2 database servers), but sometimes that's not feasible (budget constraints, whatever). Now, CS's orginal question... it should be possible just to dump and load the tables from the vendor provided copy of mysql into your existing instance. You'll need to check version numbers though (if the vendor product isn't using a recent MySQL, you're probably SOL and will have to go with 2 instances). Mark R. Andrachek, Jr. Analyst I Federal Reserve Bank of Richmond [EMAIL PROTECTED] (804) 697-7971 Francisco Reinaldo [EMAIL PROTECTED] 06/13/2002 10:44 AM To: [EMAIL PROTECTED], Chris Stefanick [EMAIL PROTECTED], MySQL Support [EMAIL PROTECTED] cc: Subject:RE: setting up two instances of mySQL Hi Chris, I am Tom, you know your manager, did you say that I am wrong!!! Just kidding :-). Well I cannot find any good reason for having two databases in two different instance. Do you have two Oracles or Microsoft SQL Server instances in the computer? Nope. The only reason when that is acceptable, is when you want to keep two version of the same database engine. Like having 3.23 and 4.0. Having two MySQL instances is going to complicate things making everything more difficult to maintain and install. Good Luck. --- Cal Evans [EMAIL PROTECTED] wrote: The pros are you can run them under separate user/group ids therefore you can make it much harder for someone with access to only one to get to the other's data. The cons are that you will have 2 copies running therefore it will take longer to maintain. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -Original Message- From: Chris Stefanick [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 7:56 AM To: MySQL Support Subject: setting up two instances of mySQL I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? Thanks so much, CS - 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 - 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 __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com - 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 - 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
setting up two instances of mySQL
I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? Thanks so much, CS - 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
RE: setting up two instances of mySQL
The pros are you can run them under separate user/group ids therefore you can make it much harder for someone with access to only one to get to the other's data. The cons are that you will have 2 copies running therefore it will take longer to maintain. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -Original Message- From: Chris Stefanick [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 7:56 AM To: MySQL Support Subject: setting up two instances of mySQL I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? Thanks so much, CS - 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 - 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
Re: setting up two instances of mySQL
Chris, Wednesday, June 05, 2002, 3:55:52 PM, you wrote: CS I have one product already using a mySQL database. We just inherited a new CS product (via an acquisition) that uses it's own mySQL database which we're CS going to stick on the same server. My manager wants me to setup a second CS instance of mySQL on the machine for the new product's database. I don't CS see the point. Why not just have both databases running under the same CS instance of mySQL? Which brings me to my question. What are the pros and CS cons of setting up multiple instances of mySQL on the same machine? In general you can't use more than one data dir for one MySQL server, but you can create another dir for your database and create a symlinks to this dir. CS Thanks so much, CS CS -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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
Re: setting up two instances of mySQL
- Original Message - From: Chris Stefanick [EMAIL PROTECTED] To: MySQL Support [EMAIL PROTECTED] Sent: Wednesday, June 05, 2002 2:55 PM Subject: setting up two instances of mySQL I have one product already using a mySQL database. We just inherited a new product (via an acquisition) that uses it's own mySQL database which we're going to stick on the same server. My manager wants me to setup a second instance of mySQL on the machine for the new product's database. I don't see the point. Why not just have both databases running under the same instance of mySQL? Which brings me to my question. What are the pros and cons of setting up multiple instances of mySQL on the same machine? I read the reply about the ability to run under two different users. True. Plus the advantage would be that both administrators of the two products can each have full root-access to their MySQL server. That, to me, would be the main pro. But I cannot help but feel this is like running a separate instance of qpopper for each individual mailbox. It will shave an additional ~ 13-30 MB off your resources, and if you only take a few moments to set up the privilege system properly (removing anonymous users, making sure all users have passwords, etc), there should really be no concern for security. And be careful who you give the file privilege to. Most security holes really stem from an improper grasp of the privilege system. Like forgetting to specifically revoke privileges for a table when you delete that table, and not realizing the alter privilege may be used to subvert the privilege system by renaming tables, etc. But if you took care of those, I truly see no real security issue. Plus, if you start your server with the --safe-show-database option, SHOW DATABASES will only return those databases for which the user has some kind of privilege. More experienced users may be aware of nifty security holes that I am unaware of; but under normal circumstances, my preference is to not run a separate instance for each separate database. YMMV, as they say. - Mark System Administrator Asarian-host.org --- If you were supposed to understand it, we wouldn't call it code. - FedEx - 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
