Install MySQL - Revision history

Vmurrell at 16:14, 30 October 2025

2025-10-30T16:14:50Z

Vmurrell at 12:34, 11 October 2025

2025-10-11T12:34:50Z

Vmurrell at 15:49, 4 September 2023

2023-09-04T15:49:27Z

Plazarou: /* Overview */

2022-12-21T12:43:08Z

‎Overview

Plazarou: /* Overview */

2022-12-21T12:42:59Z

‎Overview

Plazarou: /* Installing MySQL 5.7 */

2022-12-21T12:40:51Z

‎Installing MySQL 5.7

Plazarou at 12:38, 21 December 2022

2022-12-21T12:38:54Z

Plazarou: /* Versions and Permissions */

2022-10-26T07:40:05Z

‎Versions and Permissions

Plazarou: /* Versions and Permissions */

2022-05-25T16:32:25Z

‎Versions and Permissions

Plazarou: /* Troubleshooting MySQL */

2022-05-24T10:45:12Z

‎Troubleshooting MySQL

@@ Line 1: / Line 1: @@
-[[Category:How_To]]
+[[Category:Fusion Registry Installation]]
 =Overview=
 Fusion Registry needs an operating database to store the structural metadata, configuration settings and other operating information like audit logs. MySQL, Oracle and SQL Server are supported. If you already have one of those services available, use that and simply create a new schema for Fusion Registry to use.

@@ Line 10: / Line 10: @@
 For version 10.X of the Fusion Registry MySQL version 8 may not be used.
-For versions of the Fusion Registry up to version 11, the MySQL database or eqivalent services like MariaDB must be MySQL compatible.
+For versions of the Fusion Registry up to version 11, the MySQL database or equivalent services like MariaDB must be MySQL compatible.
 For versions of the Fusion Registry from version 11 onwards, MySQL version 8 may be used.

@@ Line 1: / Line 1: @@
 [[Category:How_To]]
 =Overview=
 Fusion Registry needs an operating database to store the structural metadata, configuration settings and other operating information like audit logs. MySQL, Oracle and SQL Server are supported. If you already have one of those services available, use that and simply create a new schema for Fusion Registry to use.

← Older revision		Revision as of 12:43, 21 December 2022
Line 4:		Line 4:

	'''Important Note: ''' From version 11.8.0 onwards, the Fusion Registry will no longer ship with a MySQL connector due to licensing issues. The Fusion Registry can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of Fusion Registry, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.8.0 or later. If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start the Registry and communicate with a MySQL database.		'''Important Note: ''' From version 11.8.0 onwards, the Fusion Registry will no longer ship with a MySQL connector due to licensing issues. The Fusion Registry can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of Fusion Registry, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.8.0 or later. If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start the Registry and communicate with a MySQL database.
−

	==Versions and Permissions==		==Versions and Permissions==

← Older revision		Revision as of 12:42, 21 December 2022
Line 3:		Line 3:
	Fusion Registry needs an operating database to store the structural metadata, configuration settings and other operating information like audit logs. MySQL, Oracle and SQL Server are supported. If you already have one of those services available, use that and simply create a new schema for Fusion Registry to use.		Fusion Registry needs an operating database to store the structural metadata, configuration settings and other operating information like audit logs. MySQL, Oracle and SQL Server are supported. If you already have one of those services available, use that and simply create a new schema for Fusion Registry to use.

−	From version 11.8.0 onwards, the Fusion Registry will no longer ship with a MySQL connector due to licensing issues. The Fusion Registry can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of Fusion Registry, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.8.0 or later. If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start the Registry and communicate with a MySQL database.	+	'''Important Note: ''' From version 11.8.0 onwards, the Fusion Registry will no longer ship with a MySQL connector due to licensing issues. The Fusion Registry can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of Fusion Registry, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.8.0 or later. If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start the Registry and communicate with a MySQL database.

@@ Line 18: / Line 18: @@
 =Installing MySQL 5.7=
 Download and install [https://dev.mysql.com/downloads/windows/installer/5.7.html MySQL 5.7 Community].
 =Creating the Fusion Registry schema=

← Older revision		Revision as of 16:32, 25 May 2022
Line 4:		Line 4:

	==Versions and Permissions==		==Versions and Permissions==
		+
		+	For version 10.X of the Fusion Registry MySQL version 8 may not be used.
		+
	For versions of the Fusion Registry up to version 11, the MySQL database or eqivalent services like MariaDB must be MySQL 5.7 compatible.		For versions of the Fusion Registry up to version 11, the MySQL database or eqivalent services like MariaDB must be MySQL 5.7 compatible.

@@ Line 44: / Line 44: @@
 MySQL 5.X appears to have the value of local_infile set to "true" or "ON" by default, whereas MySQL 8.X appears to have this value set to "false" or "OFF"
-To enable the loading of data, you will need to set your MySql database to enable the loading of data via "LOAD DATA LOCAL INFILE".  This is performed via the editing of the config file,
+To enable the loading of data, you will need to set your MySql database to enable the loading of data via "LOAD DATA LOCAL INFILE".  This is performed via the editing of the config file, '''my.cnf''' and add:
-, run the following:
+Alternatively you may find the following works. If you run the following command:
    SHOW GLOBAL VARIABLES LIKE 'local_infile';