MySQL 8.0 FAQ: General MySQL 5.0 achieved General Availability (GA) status with MySQL 5.0.15, which was released for production use on 19 October 2005. Active development for MySQL 5.0 has ended. Due to the many new and important features we were introducing in this MySQL version, we decided to start a fresh new series. As the series numbers 6 and 7 had actually been used before by MySQL, we went to 8.0. Yes. See Section 13.2.11, “Subqueries” . Yes. For the syntax required to perform multiple-table updates, see Section 13.2.13, “UPDATE Statement” ; for that required to perform multiple-table deletes, see Section 13.2.2, “DELETE Statement” . A multiple-table insert can be accomplished using a trigger whose  FOR EACH ROW  clause contains multiple  INSERT  statements within a  BEGIN ... END  block. See Section 25.3, “Using Triggers” . No. However, MySQL has an  AUTO_INCREMENT  system, which in MySQL 8.0 can also handle inserts in a multi-source replication setup. With the  auto_increment_increment  and auto_increment_offset  system variables, you can set each server to generate auto-increment values that don’t conflict with other servers. The  auto_increment_increment  value should be greater than the number of servers, and each server should have a unique offset. Yes, see Section 11.2.6, “Fractional Seconds in Time Values” . Yes. MySQL is fully multithreaded, and makes use of all CPUs made available to it. Not all CPUs may be available; modern operating systems should be able to utilize all underlying CPUs, but also make it possible to restrict a process to a specific CPU or sets of CPUs. On Windows, there is currently a limit to the number of (logical) processors that  mysqld  can use: a single processor group, which is limited to a maximum of 64 logical processors. Use of multiple cores may be seen in these ways: mysqld  is a single-process program, not a multi-process program, and does not fork or launch other processes. However,  mysqld  is multithreaded and some process-reporting system utilities display 5232 •If the database is I/O-bound (indicated by CPU consumption less than capacity), adding more CPUs is futile. If the database is partitioned into an I/O-bound part and a CPU-bond part, adding CPUs may still be useful. •A few background threads make limited use of extra cores; for example, to keep background I/O tasks moving. •A single core is usually used to service the commands issued from one session. A.1.2. Why did MySQL version numbering skip versions 6 and 7 and go straight to 8.0? A.1.3. Can MySQL 8.0 do subqueries? A.1.4. Can MySQL 8.0 perform multiple-table inserts, updates, and deletes? A.1.5. Does MySQL 8.0 have Sequences? A.1.6. Does MySQL 8.0 have a  NOW()  function with fractions of seconds? A.1.7. Does MySQL 8.0 work with multi-core processors? A.1.8. Why do I see multiple processes for  mysqld ?