Type of MYSQL used in Daily Production Environment
Hi,
I just completed the INSTALLATION of MYSQL (by the help of EE’ s Experts). There are some questions that I need to clarify.
There are 5 types of installation: FULL, Server, Client Only and 2 other types
My questions: Which types are usually USED in the daily production Environment? (Would you explain a little bit why please?)
Thank you
tjie
I just completed the INSTALLATION of MYSQL (by the help of EE’ s Experts). There are some questions that I need to clarify.
There are 5 types of installation: FULL, Server, Client Only and 2 other types
My questions: Which types are usually USED in the daily production Environment? (Would you explain a little bit why please?)
Thank you
tjie
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
tjie:
What platform are you installing it on? Usually the choices I've seen are: Typical, Complete, and Custom. Typical installs the MySQL server, the mysql command-line client, and the command-line utilities. Complete installs embedded libraries, benchmarks, and support scripts which are needed in a typical IT environment. Custom allows you to select any and all features available in the Complete install.
For a typical installation, I would recommend 'Typical.'
AielloJ
What platform are you installing it on? Usually the choices I've seen are: Typical, Complete, and Custom. Typical installs the MySQL server, the mysql command-line client, and the command-line utilities. Complete installs embedded libraries, benchmarks, and support scripts which are needed in a typical IT environment. Custom allows you to select any and all features available in the Complete install.
For a typical installation, I would recommend 'Typical.'
AielloJ
Full - Has both client components and server components, leaves out the extra developer bits
Server - leaves out the client only bits
Client - leaves out the server bits
Developer Default - gives you most everything from Full plus developer stuff
Custom - lets you pick an choose components.
The answer to your other question is a bit more involved.
In production, on a server, you'd install the Server and leave off the rest. On the client, just the client bits. You could also choose custom and pick and choose the specific parts you want (if you have a good understanding of what you're doing with the package sets).
The developer portions should be left off of any production environment as they often include debug checked builds and other things that slow performance in a production environment.
Server - leaves out the client only bits
Client - leaves out the server bits
Developer Default - gives you most everything from Full plus developer stuff
Custom - lets you pick an choose components.
The answer to your other question is a bit more involved.
In production, on a server, you'd install the Server and leave off the rest. On the client, just the client bits. You could also choose custom and pick and choose the specific parts you want (if you have a good understanding of what you're doing with the package sets).
The developer portions should be left off of any production environment as they often include debug checked builds and other things that slow performance in a production environment.
I think that even on web hosting, 'Full' is the normal installation so that the admins for the web hosting company can set up users and databases for clients. Note that things like the ODBC connector and MySQL Workbench are not part of any of these installs, they are additional downloads if you need them.
The Windows 5.6 GUI installer actually includes (depending on selection) the ODBC connector (as well as C++, .NET, C, and Java). The Workbench is there also...
Here's the install screen from the MySQL dev site
Here's the install screen from the MySQL dev site
Premium Content
You need an Expert Office subscription to comment.Start Free Trial