Your SQL statements must be valid for the syntax expected by the target relational system. In particular, object delimiters may vary between systems.
NOTE: The proper syntax depends on your database system. Please consult the documentation for your product for details.
Tip: Although some relational systems do not require object delimiters around column names, it is recommended that you add them to all applicable objects.
Tip: Avoid using column type identifiers (e.g.
int) and other SQL keywords as object names. Some systems may generate invalid SQL errors.
NOTE: In the following sections, Oracle syntax is used in the examples. Please modify the examples for your target system.
Supported syntax by datastore
Individual datastores may have differences in the supported syntax. For more information, please see the documentation for your datastore.
Here are some basic SQL examples to get started.
If your select statement results in multiple columns with same name, the query fails to validate or fails on execution, such as selecting all columns in a JOIN. In these cases, columns must be properly aliased.
NOTE: This error will be caught either during validating or during dataset import.
For example, in the following JOIN, the
DEPARTMENT tables have column names
The above query generates an error. Columns must be properly aliased, as in the following:
Collect whole table
Multi-line statement for imported datasets
The following example uses a multi-line SQL sequence to import a dataset:
NOTE: Multi-line SQL support is considered an advanced use case. This feature must be enabled.
The following example inserts values in the
TABLE_INVENTORY table and then queries the table. It utilizes Oracle syntax:
This page has no comments.