You can export LGTM analysis data to an external SQL database, allowing you to use the data in a business intelligence (BI) tool such as Tableau or QlikView. For full details, see Exporting LGTM analysis data.
Occasionally you may have to start over again and re-export LGTM analysis data to a BI database from scratch. Usually you only have to do this if you switch the output destination to an empty database.
Exporting to a new database after a database schema change
The format of the exported data, and the schema of the database itself, changed completely for version 1.17 of LGTM Enterprise. As a result, if you upgrade LGTM Enterprise from a version before 1.17, you must export BI data to a new, empty database after upgrading. BI export is automatically disabled during the 1.16–1.17 upgrade. This allows you time to set up a new database after upgrading. You can then go to LGTM's administration interface, specify the connection details for a new database, and re-enable BI export—see Exporting LGTM analysis data.
To populate the new database with data that was previously available in your BI tool, you must then re-export BI data from scratch.
Re-export all analysis data
In the LGTM administration interface:
Go to the
If you've not already done so, enter the Database connection string for an empty database and click Submit.
If data export is not already enabled, click Enable.
The message box says: "Enabled the BI export."
You can only enable data export after you have submitted a valid connection string.
LGTM Enterprise creates a task to start exporting data for all analyzed revisions of all projects to the specified database. The export operation is split into many small tasks to prevent the database from being locked for an extended period—for details, see What happens when data export is enabled?
If you have a large code base with a lot of analyzed history, the BI export may take a considerable amount of time. In this situation you will not see the complete picture in your BI tool immediately.
Data is not re-exported in any guaranteed order.
Re-populate the HR table
human_resources table in the BI database is available for you to populate with person data from your HR system. If you have previously populated this table you must do so again when you export analysis data to a new BI database.
For details of uploading the
Input_HumanResourcesData.csv file, see Loading HR data into the BI database.
The BI database schema
For details of the tables and fields in the BI database schema, see Querying the BI database in the user-level help.