SQL DM for MySQL uses SQLite for storing all the data. With 'data' - we are referring to:

  • Data collected from MySQL servers (stored in the database file mysql.data).
  • Data collected from the operating system (currently available for Linux only, stored in the database file system.data).
  • Data captured from 'sniffing' (stored in the database file sniffer.data).
  • Data captured from 'CSO's (stored in database file udo.data).
  • Data captured for events (stored in events.data).
  • Data captured when a Real-Time session is started and saved (stored in the realtimedata folder: rt_name.data).
  • Data related to MySQL server connection (stored in connection.data).
  • Also, for faster retrieval in future, SQL DM for MySQL stores the cached data (stored in cache.data).

There is one of each of those database files for every connection except for events.data that is common to all the servers.

Where can you find this data?

Below, you can find the default paths for the data collected by SQL DM for MySQL for the first connection created by SQL DM for MySQL:

In windows systems


In Linux systems

-   RPM: /usr/local/MONyog/data/0001
-   Tar: In the same directory where MONyog was 'untarred'.

How to view existing schema and data?

You can view the existing schema and data by using a SQLite client. In addition to the official SQLite command-line client there are simple GUI clients available SQLite Manager (This is a plugin for the Firefox browser and works on all platforms, but there are more GUI clients available for download - mostly for Windows. Most Linux distributions ship with some database client software that handles SQLite).

Schemas may be subject to change. We may add/remove columns, change data types, change indexes etc. with new releases. When we do that, you can check-in release notes and you can open the database with the tools mentioned to see the columns.

IDERA ProductsPurchase | Support | Community | Resources | About Us | Legal
  • No labels