Connecting to generic JDBC
A more flexible approach for databases that don’t have a dedicated connector in Tellius
Last updated
Was this helpful?
A more flexible approach for databases that don’t have a dedicated connector in Tellius
Last updated
Was this helpful?
The generic JDBC connector allows you to integrate any database or data source for which you have a JDBC-compliant driver—even if it isn’t listed among Tellius’s native connectors. By specifying the JDBC driver class and crafting a valid JDBC connection string, Tellius can communicate with that data source, browse tables, and ingest data.
You must provide the Driver class (e.g., com.mysql.jdbc.Driver) instead of relying on a preconfigured driver.
You construct the entire JDBC URL (e.g., jdbc:postgresql://host:port/dbName) to define the connection.
Supports virtually any database with a functional JDBC driver, even if not officially listed.
If your driver is not already on the Tellius classpath, you may need to upload or install it separately.
URL: The JDBC connection string for your target data source. Informs Tellius exactly how to reach and authenticate with your database, including hostname, port, and any query parameters required by that driver. E.g.:
Driver: The fully-qualified Java driver class (e.g., com.mysql.jdbc.Driver, org.postgresql.Driver, etc.). Tells Tellius which JDBC driver to load. This class must be present on the classpath or provided to Tellius’s environment, or the connection will fail.
User: The username for authenticating with the target database. If your database requires login credentials, supply them here. If the database is configured for token-based or OS-based authentication, you may skip it.
Password: Required for most JDBC databases unless they’re configured for password-less or token-based access.
Datasource Name: A user-friendly name for this connect
Save and Browse Host: Saves these settings and attempts to establish a connection. If successful, you can browse available schemas or tables.
Use validated datasource connection details: When enabled, it reveals a dropdown to choose from existing, previously configured JDBC connections.
Select datasource: Lists all pre-validated JDBC connections. Select the one you want to reuse and all the fields will be filled automatically as configured.
Browse Host: Similar to “Save and Browse Host”, but now it just navigates forward using the chosen existing connection’s parameters.
After establishing a connection, you will see options to load data from JDBC tables.
Select a table: Displays all available tables under the chosen JDBC SQL schema. Pick the tables you need for analysis. If there are many tables, you can narrow down your selection.
Search for table: Filters the displayed tables based on your search term.
Import: Imports the selected table(s) into Tellius.
If you prefer more granular control or want to write your own SQL queries to load precisely the data you need, switch to "Custom SQL" tab.
Table filter: Helps locate a particular table by name before writing your SQL.
Select a table: Choose a table name to use in your custom query.
Query: A field for your custom SQL statement (e.g., SELECT * FROM SYS.WRI$_DBU_CPU_USAGE).
Preview: Executes the SQL query and displays a few sample rows of the data you’re about to import in the “Dataset Preview” area. Allows you to validate that the query returns the correct data before fully importing it. This helps catch syntax errors or incorrect filters early.
Import: Once satisfied with the preview, click Import to load the data returned by the SQL query into Tellius.
Once you import, you’ll have the option to refine how the dataset is handled:
Dataset name: Assign a valid name to your new dataset (e.g., XYZ_THRESHOLD). Names should follow the allowed naming conventions (letters, numbers, underscores, no leading underscores/numbers, no special chars/spaces).
Connection Mode When the Live checkbox is selected, the queries will be fetched from the database each time, and the data will not be copied to Tellius. Live mode ensures the most up-to-date data at the cost of potential query latency.
When Live mode is enabled, then only Create Business View option will be displayed.
Copy to system: If enabled, copies the imported data onto Tellius’s internal storage for faster performance. Reduces dependency on the source database’s speed and network latency. Good for frequently queried datasets.
Cache dataset in memory: If enabled, keeps a cached copy of the dataset in memory (RAM) for even faster query responses. Memory caching dramatically reduces query time, beneficial for dashboards and frequently accessed data.
When only one table is imported, the following options will also be displayed:
Partition column: The column used as a basis for partitioning.
Number of partitions: How many segments to break the data into. (e.g., 5 partitions)
Lower bound/Upper bound: Approximate value range in the partition column to evenly distribute data.
Create Business View: If enabled, after loading data, you will be guided into the Business View creation stage.
Click on Load to finalize the process. After clicking Load, your dataset appears under Data → Dataset, ready for exploration, preparation, or business view configuration. Else, click on Cancel to discard the current importing process without creating the dataset.
After the dataset is created, you can navigate to "Dataset", where you can review and further refine your newly created dataset. Apply transformations, joins, or filters in the Prepare module.
Partitioning: If enabled, it splits a large dataset into smaller logical chunks (partitions). Improves performance on large tables, enabling parallel processing and faster load times. For more details, check out dedicated page on Partitioning.
