Skip to main content Skip to complementary content

Saving the queries executed on indicators

Before you begin

At least one analysis with indicators has been created in the Profiling perspective.

About this task

From Talend Studio and in the Data Explorer perspective, you can view the queries executed on different indicators used in an analysis. From the data explorer, you will be able to save the query and list it under the Libraries > Source Files folders in the DQ Repository tree view.

To save any of the queries executed on an indicator set in a column analysis, do the following:

Procedure

  1. In the column analysis editor, right-click any of the used indicators to open a contextual menu.
    Contextual menu of an analyzed column from the Analyzed Columns section.
  2. Select View executed query to open the data explorer on the query executed on the selected indicator.
    If the Data Explorer perspective is missing from Talend Studio, you must install certain SQL explorer libraries that are required for data quality to work correctly, otherwise you may get an error message.
    For further information about identifying and installing external modules, see Installing external modules to Talend Studio.
    Query opened in the Data Explorer perspective.
    Information noteNote: The data explorer does not support connections which has empty user name, such as Single sign-on of MS SQL Server. If you analyze data using such connection and you try to view the executed queries in the Data Explorer perspective, a warning message prompt you to set your connection credentials to the SQL Server.
  3. Click the save icon on the editor toolbar to open the Save the Source file dialog box
    Overview of the Save the Source file dialog box.
  4. Select the Source Files folder or any sub-folder under it and enter in the Name field a name for the open query.
  5. Click OK to close the dialog box.
    The selected query is saved under the selected folder in the DQ Repository tree view.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here