MySQL version Selection

MySQL open-source database has multiple important branches: MySQLCluster, MySQL5.1, MySQL5.5, and MySQL6.2. each branch has the same

MySQL open-source database has multiple important branches: MySQL Cluster, MySQL 5.1, MySQL 5.5, and MySQL. 2. Each branch has the same

MySQL open-source database has multiple important branches: MySQL Cluster, MySQL 5.1, MySQL 5.5, and MySQL 6. 2. each branch has the same MySQL database version: Development version, Alpha version, Beta version, RC version, and GA version.

The Development version, Alpha version, and Beta version are generally not used in the project. they certainly have major problems or some functions are not fully implemented. in most cases, the RC version is not allowed to be used in the production environment. After all, it is only a small version before the production version is released. similarly, we must carefully select the GA version of the MySQL database. after all, open-source community products have not been strictly tested and may have weak stability than commercial products.

The process for selecting the GA version of MySQL database:

Since Oracle acquired SUN and its wholly-owned subsidiary MySQL AB, MySQL AB has no longer contributed source code to the open-source community. at the same time, with the departure of many founders and technicians, we must carefully select the new version released by MySQL AB. Do not blindly trust the test report officially provided by MySQL AB. we recommend that you refer to the following MySQL database GA version selection process:

Analyze whether the enterprise business needs to use the basic functions and features of MySQL. The key research areas are MySQL replication, partition table, and Plugin-innodb.

The first GA version of the MySQL database product line should be available for at least 10 months before being used in the production environment.

The latest GA version of the MySQL database product line is generally not the first choice. It may be 3 ~ later than the latest version ~ Four versions of the GA database.

Read the GA version of the target database carefully. If a large number of bugs are modified based on the previous version, the GA version carefully reads the information of the first version after the GA version of the target database, if the BUG information to be modified is very large, discard the target version and push forward a version number as the target version.

Follow the steps described in step 4 and Step 5 to select a version that is later than the selected version. The number of bugs is not significant, and there are very few serious bugs, and it is not the latest GA version.

Read in detail 2 ~ after the selected database GA version ~ The BUG fix information of the three versions is mainly related to the target GA version, and how to reproduce it and find solutions to circumvent it.

Perform functional and performance tests on the GA version selected in the above seven steps, combined with the features that may be required by the enterprise business.

The selected database GA version, as an internal development and testing database environment, usually takes about 3-6 months for trial run.

Non-core businesses of enterprises can adopt the new GA version.

After the above 10 procedures, if there are no major functional bugs or performance bottlenecks, you can start to consider as the backend database of all business data services.

Many full-time DBAs in enterprises may not have the time, energy, or resources to select versions, and may not be willing to spend so much time. some enterprises may need to select a database GA version. Some enterprises do not have a full-time DBA, but are replaced by O & M or development engineers, however, they may not be able to select database software versions. are there any shortcuts for choosing the GA version of the MySQL database? The answer is yes. you can pay more attention to the DBAs of some large companies or well-known DBAs in the industry. You can consult them through multiple channels or consult internal personnel directly, learn the version of their core business database.

Alpha version: generally only runs within a software development company and is not publicly available. It is mainly for developers to develop their own products.

Perform tests and check whether the product has any defects or errors. Verify the product features and manuals and user manuals.

Consistent or not. MySQL is an open-source product for source code development.

Developers, enthusiasts, and users participate in software development, testing, and manual writing. Therefore

Deploy the source code and products of this version so that anyone can participate in development or testing, or even write and

Modify user manual.

Beta: products that have completed functional development and all tests do not have great functionality or performance.

BUG, and invite or provide users with experience and testing, in order to more comprehensively test the lack of software

Problem;

RC version: A minor version or candidate version before the production environment is released. It is collected by users to test the Beta version.

The bugs or deficiencies found are fixed and improved based on the collected information;

GA version: the version of the software product officially released, also known as the product of the production version. Generally

Select the GA version of MySQL software for real production environments;

1) to analyze the business of this enterprise, you need to use the basic functions and features of MySQL. The key features are MySQL replication, partition tables, and Plugin-innodb;

2) The first GA version of the MySQL database product line should be available for at least 10 months and then be used in the production environment;

3) The latest GA version of the MySQL database product line. Generally, three or four versions of GA version databases are removed as optional targets;

4) carefully read the selected target database GA version. If a large number of BUG information is modified for the previous version, the GA version should be carefully selected;

5) carefully read the first version of the target GA database. If the BUG information is very large, directly discard the target version and push forward a version number as the target version;

6) follow the steps described in steps 4 and 5 until a version after the selected version has not been modified much, there are very few serious bugs, and it cannot be the latest database product of GA version;

7) read in detail the BUG fix information of 2-3 versions after the selected database GA version, mainly related to the target GA version, and find a way to reproduce the BUG and find a way to circumvent it;

8) for the GA version selected in the above seven steps and functions that may be required by the enterprise's business, functional testing and performance testing of business simulation are required;

9) The selected database GA version is used as an internal development and testing database environment and takes about 3-6 months;

10) Priority should be given to non-core businesses of enterprises to adopt the new version of database GA software;