Switching between different contexts of the same connection - Cloud - 8.0

Talend Studio User Guide

Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Studio
Design and Development
Last publication date
Available in...

Big Data Platform

Cloud API Services Platform

Cloud Big Data Platform

Cloud Data Fabric

Cloud Data Management Platform

Data Fabric

Data Management Platform

Data Services Platform

MDM Platform

Real-Time Big Data Platform

When you create more than one context for the same database or file connection, the menu Switch context is accessible from the connection. This menu enables you to select the context on which you want to execute the current analysis.

Before you begin

Multiple contexts have been defined for a connection in the Profiling perspective. For more information, see Creating multiple contexts for the same connection.

Make sure that the database name, the schema name or the catalog name is defined in the wizard. When you switch between different contexts, this enables you to retrieve the correct database structure.


  1. In the DQ Repository tree view, expand Metadata > DB connections or Metadata > File Delimited.
  2. Right-click the connection exported as a context and select from the contextual menu Switch context.
    Contextual menu of a DB connection.

    The Choose context dialog box is displayed.

  3. Select from the list the context you want to set for the current connection, and then click OK to close the dialog box.
    Overview of the Choose context dialog box.
    A confirmation message is displayed prompting you to refresh the connection editor.
  4. Click OK to close the message.
    The context has been changed accordingly for the current selection.
    For detailed information on centralizing the contexts and variables to be used in data integration Jobs or data quality analyses, see Centralizing database metadata.