How to Read Datameer's Application Database Schema

Goal

Understand Datameer's application database schema so you can integrate Datameer into an existing enterprise environment or 3rd party tools using your own scripts and software. 

Learn

Datameer recommends accessing Datameer using the REST API for automation purposes

The MySQL instance isn't intended for direct or public access. While you can technically create a custom query, it is not recommended to use this approach in most cases. If the database schema changes in future releases, custom scripts might not work as specified. Since Datameer assumes that there are no external dependencies, those schema changes might occur without notification.

The Datameer service depends on the MySQL database, and it is used for constant writes for workbooks, permission changes, job execution, and scheduling, among other things. Therefore, direct changes to the database are not recommended. 

Furthermore not all information can be maintained within the database. For example, job history is stored up to only 28 days.

Further Information

If you still want to access the application database directly, you could consider 3rd party tools such as SchemaCrawler or SchemaSpy to create an entity relationship diagram

You might also find the following articles helpful:

Attachement