Skip to main content

ELT Script Runner

The ELT Script Runner is a Nexla utility connector that executes an ELT (Extract, Load, Transform) SQL script directly against a data warehouse or database on a schedule. Rather than pulling data into Nexla for transformation, it pushes the query down to the underlying engine, letting transformations run where the data already lives. You select the type of database to run against, choose an existing Nexla credential for that database, provide the SQL to execute, and set how often the job should run.

ELT Script Runner icon

Power end-to-end data operations for your ELT Script Runner API with Nexla. Our bi-directional ELT Script Runner connector is purpose-built for ELT Script Runner, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ELT Script Runner or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ELT Script Runner workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The ELT Script Runner does not use its own vendor credential. Instead, it runs your SQL script using an existing Nexla database credential for the engine you want to execute against. Before configuring this connector, ensure the following:

  • A supported database or warehouse: The connector can run scripts against Redshift, MySQL, PostgreSQL, Snowflake, Oracle DB, Oracle Autonomous Data Warehouse, Microsoft SQL Server, Google BigQuery, Hive, or Presto.

  • A Nexla credential for that database: You must already have (or create) a Nexla credential for the specific database engine your script targets. This credential supplies the connection details and authentication that Nexla uses to reach the database. For instructions on setting up a credential for your engine, see the connector guide for that database.

  • A user with permission to run the script: The account behind the database credential must have the privileges required by your SQL statements — for example, SELECT on the source tables and, for transformations that write results, the appropriate INSERT, UPDATE, or CREATE privileges on the target objects.

  • The SQL script to execute: Prepare and validate the ELT query you want to run so it produces the intended result when executed directly against the database.

Authenticate​

The ELT Script Runner authenticates through the Nexla database credential you select for the chosen database type. There are no connector-specific credential fields to enter for the Script Runner itself; authentication is handled entirely by the underlying database credential.

Create a credential in Nexla​

  1. After selecting the ELT Script Runner as your data source, choose the target engine from the Database Type pulldown menu. The credential options shown next are filtered to match the selected database type.

  2. Select an existing credential for that database, or click the Add Credential tile to open the Add New Credential overlay and create one.

  3. When creating a new credential, enter a name in the Credential Name field and a short, meaningful description in the Credential Description field, then supply the connection and authentication details required by your chosen database engine.

  4. Click the Save button at the bottom of the overlay. The credential will appear as a tile and can be selected for use with the ELT Script Runner.

The credential fields you complete depend on the database engine you select. Refer to the connector guide for your specific database (for example, Snowflake, PostgreSQL, or Google BigQuery) for the exact fields and where to obtain their values.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ELT Script Runner connector tile, then select the credential that will be used to connect to your database, and click Next; or, create a new credential for use in this flow.

Endpoint templates​

The ELT Script Runner provides a single template that runs your SQL script against the selected database on a schedule.

ELT Script Runner

Configure this connector to run an ELT script using Nexla. Choose your underlying database connection type and the ELT script to execute.

  • Database Type: Select the type of database you want to run your query on. Supported engines are Redshift, MySQL, PostgreSQL, Snowflake, Oracle DB, Oracle Autonomous Data Warehouse, Microsoft SQL Server, Google BigQuery, Hive, and Presto.
  • Credential: Select the Nexla credential for the database you chose. The available credentials are filtered to match the selected database type.
  • SQL Query: Enter the SQL statement to execute in the SQL editor. This is the ELT script that Nexla runs directly against the selected database.
  • Frequency: Set how often the job runs. Nexla executes the script on the schedule you define.

Because the script runs directly on the target database, the credential you select must have the privileges required by your statements — read access on the source tables and, for statements that write results, permission to create or modify the target objects.

Once the script and schedule have been configured, click the Test button to validate the query against the selected database before saving. When the configuration is correct, click the Create button in the upper right corner of the screen to save and create the new ELT Script Runner data source. Nexla will run the script on the defined schedule and organize any returned data into one or more Nexsets.