Manage the MySQL Connector

This applies to: Visual Data Discovery

The Symphony MySQL connector lets you access the data available in MySQL databases using the Symphony client. The Symphony MySQL connector supports MySQL versions 5.6 - 8.0.

Before you can establish a connection from Symphony to MySQL storage, a connector server needs to be installed and configured. See Manage Connectors and Connector Servers for general instructions and Connect to MySQL in Visual Data Discovery for details specific to the MySQL connector.

After the connector has been set up, you can create data source configurations that specify the necessary connection information and identify the data you want to use. See Manage Visual Data Discovery Data Source Configurations for more information. After data sources are configured, they can be used to create dashboards and visuals from your data. See Create Data Discovery Dashboards.

Feature Support

Connector support for specific features is shown in the following table.

Key: Y - Supported; N - Not Supported; N/A - not applicable

Feature	Supported?
Admin-Defined Functions	Y
Box Plots	N
Custom SQL Queries	Y
Derived Fields (Row-Level Expressions)	Y
Distinct Counts	Y
Fast Distinct Values	N/A
Group By Multiple Fields	Y
Group By Time	Y
Group By UNIX Time	Y
Histogram Floating Point Values	Y
Histograms	Y
Kerberos Authentication	N
Last Value	Y
Live Mode and Playback	Y
Multivalued Fields	N/A
Nested Fields	N/A
Partitions	N
Pushdown Joins for Fusion Data Sources	Y
Schemas	Y
Text Search	N/A
TLS	Y
User Delegation	N
Wildcard Filters	Y
Wildcard Filters, Case-Insensitive Mode	Y
Wildcard Filters, Case-Sensitive Mode	N

Connect to MySQL in Visual Data Discovery

The MySQL connector requires a JDBC driver to be configured before you can connect to your data source.

Download and install the version latest JDBC driver from https://dev.mysql.com/downloads/connector/j/. Instructions are provided on that website.
After installing the driver, edit the MySQL properties file and change the driver path and class name properties, as shown below and as described in Add a JDBC Driver:
```
datasource.driver-config.class-name=com.mysql.cj.jdbc.Driver

datasource.driver-config.jar-path=<JDBC_driver_filepath>
```
Save the properties file and restart the connector. See Add a JDBC Driver.

Connect to MySQL in Managed Dashboards

This applies to: Managed Dashboards, Managed Reports

This article provides details on using the MySQL data provider in a Symphony data connector. The MemSQL data provider is similar and relies on the same drivers.

You can also use ODBC or JDBC drivers to connect to MySQL.

Main article: Connect to data and view it on a dashboard

Install the Driver

Linux

Download MySQL connector for .NET for .NET & Mono, and extract it to find MySql.Data.dll. If there are multiple versions of this file in different folders, locate the file in the newest netstandard or netcore folder available up to version 3.1 corresponding with the .NET Core 3.1 platform used by Symphony.

The DLL needs to be placed at this location within the Symphony instance's files:

/usr/share/dundas/bi/Files/{Instance Name}/www/BIWebsite/App_Data/ExtensionsLib/netcore/MySql.Data.dll

For a Docker image, the instance name is Container. Otherwise, you could locate the App_Data folder within your Symphony installation, create two additional subdirectories ExtensionsLib/netcore/ (if they do not exist), and place the DLL within netcore.

Ensure the permissions allow the dundasbi group to read and execute the new file (e.g., chgrp dundasbi MySql.Data.dll and chmod 751 MySql.Data.dll). Restart the Symphony service to ensure the DLL is loaded (e.g. for a Symphony instance, restart the website service).

Data Connector Settings

Create a new data connector and set Data Provider to MemSQL Database or MySQL Database as appropriate.

Connecting to MySQL

Set the remaining fields for the server, credentials, and database, and click to access additional options if needed from the expandable sections below. To see a description, hover over (or long-tap) one of the fields.

When using tenant overrides to connect to different databases, expand the Discovery section and select Single Schema to discover and use database structures without prefixing the original database (schema) name in queries.