...
While importing data, you parameterize relational tables by creating custom SQL statements to specify the dataset. By By default, when you import a table from a relational source, the
d-s-product |
---|
platform | ||
---|---|---|
|
SELECT
* statement to import the entire table. The Custom SQL enables you to customize the query to pull the data from the source system....
- A connection must be created for your target database.
- Verify that you have access to a read-only or read-write set of connections.
- For more information, see Connect to Data.
Limitations:
- The original table that is used as the default value in any custom SQL query remains the default table whenever the custom SQL dataset is used.
- During job execution on a dataset of parameterized tables, if the parameterized SQL query returns data from a table from the default table,
expects that the schema of the new table matches the schema of the original default table.D s platform - If the schemas do not match, schema mismatch errors may be reported.
- During job execution on a dataset of parameterized tables, if the parameterized SQL query returns data from a table from the default table,
- Parameterizing the column project list in the
SELECT
portion of a custom SQL statement is not supported. - Schema refresh of a parameterized dataset using custom SQL is not supported.
Create a custom SQL dataset
You can create a custom SQL dataset through the Import Data page.
Steps:
- In the
, click Library in the left nav bar.D s webapp type Portal - In the Library page, click Import Data.
- From the left side of the Import Data page, select the relational connection from which to import.
- Depending on the type of relational connection, you may need to select the database or schema to browse.
- Locate the tables to import. Take note of the table name or names.
- Click Create Dataset with SQL. The Create Dataset with SQL window is displayed.
...