Topics Map > Technology > Denodo

Denodo - Connecting to MySQL db

This article provides step-by-step instructions on how to connect to a MySQL db in Denodo.
  1. Log into Design Studio for the appropriate environment.
  2. Open your VDB (virtual database).
  3. Navigate to Connectivity then Data Sources.
  4. Select the vertical ellipses next to the 01 - Data Sources folder.
  5. Select New.
  6. Select Data source.
  7. Select JDBC.

Data Source Configuration

  1. Enter a descriptive Name with no spaces.
    NOTE: Names will automatically be converted to lowercase.
  2. For Database adapter, select the driver that corresponds to the database type you are connecting to. In this case, we'll select the MySQL driver version that matches our version of MySQL.
    NOTE: Full list of database adapters included in Denodo.
  3. Generate the Database URL based on the host, port, and database name you are connecting to. The exact format and structure of the URL will change depending on which database adapter is chosen.
  4. For Transaction isolation, choose from the following options:
    1. Database default: The Server uses the default isolation level of the database.
    2. No transactions: Disables transaction support.
    3. Read uncommitted: A transaction can read data that is not committed (dirty reads). For example, a transaction A inserts a row in a view, transaction B reads the new row and then, transaction A rollbacks.
    4. Read committed: The database keeps write locks until the end of the transaction so a transaction can read only committed data and dirty reads cannot occur. However, the database releases read locks as soon as the SELECT operation ends, so the same SELECT query may return different results in the same transaction (non-repeatable reads). For example, transaction A reads a row and transaction B changes this row. If transaction A reads this row again, it will obtain different values.
    5. Repeatable read: The database keeps read and write locks until the end of the transaction. Therefore, it avoids dirty reads and non-repeatable reads. However, this isolation level does not avoid phantom reads. This problem occurs when one transaction executes a query over a range of rows using a condition, while another transaction can simultaneously insert a row in the same range.
    6. Serializable: This is the highest isolation level and avoids dirty reads, non-repeatable reads and phantom reads by locking range of rows or the entire tables.
  5. For Authentication, choose Use login and password and the data source will connect to the database using the login and password you enter.
  6. Click Test Connection.
  7. If the test is successful, click Save to save the data source.


KeywordsDesign Studio JDBC   Doc ID137395
OwnerLearning Systems SupportGroupUI Training and Development Resources
Created2024-05-16 11:56:49Updated2024-07-03 11:32:56
SitesUniversity of Illinois Training and Development Resources
Feedback  0   0