DataGrip 2022.1 Help

Slow or incorrect introspection

Introspection is the process during which the IDE retrieves information about a database. This information is used to show the objects in the database explorer, display their DDL, suggest them during completion, and in other features for code assistance.

Sometimes introspection runs into problems. For example, it might take much longer time to introspect a database, or some objects that exist in the database do not show up in the Database Explorer. In these cases, try to use the following menu items to collect troubleshooting data and pass it on to our support team.

As you collected all the needed troubleshooting materials, consider passing them on to our support team.

Collect information by using Diagnostic tools

  • Right-click a data source and navigate to Diagnostics. Select between the following options:

    • Dump Model: generates a DataGrip-specific representation of the database structure (a database model). You can include automatically generated content by clicking the Include auto-generated content icon.

      Dump model
    • Diagnostic Refresh: reloads the metadata from the database and generates a LOG file. This information might be helpful for the support team when you think that your introspection is slow.

      Diagnostic refresh
    • Prepare Introspector Diagnostics: generates three files that include information about the data source (dataSource.txt), a module that was used to load the metadata from the database (introspector.txt), and a part of the database model (model.xml).

      This information might be helpful when introspection works incorrectly. For example, when you see something outdated or do not see new objects.

      The following screenshot shows the example output of these three files.

      Prepare introspector diagnostic
Last modified: 07 April 2022