skip to main content
Using Hybrid Data Pipeline : Using the Web UI : SQL Editor view
  

Try Now

SQL Editor view

The SQL Editor view allows users to browse schemas1 and to query data associated with a data source.
The SQL Editor view is available to users with either set of the following permissions.
*Administrator (12) permission
*WebUI (8) permission, ViewDataSource (2) permission, SQLEditorWebUI (10) permission, and, to query data sources, at least one of the following query permissions:
*UseDataSourceWithJDBC (5)
*UseDataSourceWithODBC (6)
*UseDataSourceWithOData (7)
sql editor viewsql editor view
The following table provides permissions and descriptions for actions in the SQL Editor view. To perform any action from this view, begin by selecting a data source from the Select a Data Source dropdown.
Action
Permissions
Description
Explore the schema and tables associated with the data source
WebUI (8)
ViewDataSource (2)
SQLEditorWebUI (10)
To begin, a data source must be selected from the Select a Data Source dropdown. To view schema tables, click the a schema carrot in the Schema Tree panel. Click on a table to view the details of a table in the Table Details panel. Views and procedures that reside in the schema may also be listed.
Execute a SQL statement against the data source
WebUI (8)
ViewDataSource (2)
SQLEditorWebUI (10)
At least one of the following query permissions:
*UseDataSourceWithJDBC (5)
*UseDataSourceWithODBC (6)
*UseDataSourceWithOData (7)
To begin, a data source must be selected from the Select a Data Source dropdown. To run a query against the data source, enter the SQL statement in the field provided in the Editor panel. Then click Execute to run the query. SQL query results will be returned in the Results panel.
Note: Queries made via the SQL Editor view time out after 6 minutes. Therefore, to validate a data source connection, you should execute queries that require less processing time. For large queries, only the first 200 results are shown.
1 For backend data stores that support schemas, the Metadata Exposed Schemas option can be used to restrict the exposed schemas to a single schema. Metadata Exposed Schemas only affects the metadata that is displayed in the Schema navigation pane. SQL queries can still be executed against tables in other schemas. For details, see the parameters topic for your data source type.