Table of Contents

Database Connections

This section documents how database connections are configured and used in the MIStudio Logic Editor.

Database connections allow MIStudio applications to read data from external databases, write or modify database data, and use query results as part of application logic.

Overview

Database workflows are built in the MIStudio Logic Editor using database connection and database operation components.

A typical database workflow includes:

The exact configuration depends on the database platform and authentication method being used.

Typical Database Workflow

A basic database workflow generally follows these steps:

Reading Database Data

Database read components are used for SQL statements that return data.

Common examples include:

Query results can be passed to other components in the Logic Editor.

Writing Database Data

Database write components are used when the SQL statement changes database content or structure.

Common examples include:

Use the appropriate database write component rather than a lookup component when the SQL statement performs a write operation.

JDBC Drivers

Some database platforms require an external JDBC driver.

The required driver depends on the database platform being used.

When a JDBC driver is added to an MIStudio installation, MIStudio may need to be restarted before the driver becomes available to database connection components.

Database-specific pages should document the required driver, driver class, installation location, and connection settings.

Connection Information

Database connection configuration may include:

The required fields vary by database platform.

Testing Database Logic

When testing database components, confirm that MIStudio is running the application logic in Simulating mode.

If a database query appears configured correctly but does not execute, confirm that simulation is active before changing the database configuration.

A simple query such as:

SELECT 1

can be useful for verifying that the connection is working before testing more complex SQL.

Troubleshooting

Common areas to check when a database connection does not work include:

Database-specific troubleshooting is documented on the individual connection pages.

Security

Database credentials should be handled securely.

Avoid placing passwords, access tokens, or other credentials in documentation, screenshots, source control, or other locations where they may be exposed.

Authentication methods and security requirements may differ between development, testing, and production environments.

Database Platforms

Database-specific pages provide connection and testing instructions for supported platforms.

Platform Documentation
Databricks Connecting MIStudio to Databricks

Additional database platforms can be added to this section as their MIStudio connection procedures are documented and validated.