Skip to main content
Skip table of contents

ETL+ Extract SQL Statement Panel

SQL statements in the Extract SQL Statement panel of ETL+ Extract, Transform and Load (ETL) window must work with the SQL syntax supported by the ETL+ source driver used to connect to the Source Object.

The SQL statements and syntax used in the Extract SQL Statement panel must work with the SQL syntax supported by the ETL+ Source Driver used to connect to the associated Source Object.

Proper Usage of SQL in the Extract SQL Statement

  • Use T-SQL syntax for MS SQL Server data sources.

  • For other source drivers refer to the source driver table below for the appropriate SQL variant. For instance, Use MySQL’s dialect of SQL for MySQL sources.

  • Use ANSI Standard SQL if unsure. In case of issues, be sure to check the source’s documentation and syntax since most of them have variations from the regular ANSI Standard. E.g.: see examples with Providex Joins at Sage 100 Providex SQL Syntax.

SQL Syntax to Use with Various Source Drivers and Source Systems

ETL+ Source Drivers menu

Source Driver

SQL Syntax to Use

Google Sheet




MS Access


MS Excel

MS SQL Server

Date and time data types and functions (Transact-SQL)

Microsoft T-SQL – this site


Closest related page: Acumatica Technical Details


Source database system/DBMS that ODBC connects to.



Sage 100 – ODBC Providex driver

Providex SQL Syntax

Sage 100 PxPlus Reference Manual / Providex – Guide to finding SQL documentation in this reference manual.



Text File (.csv)

Text & .CSV Data Sources Technical Details

Miscellaneous SQL Syntax Tips


    1  AS  [column2],
    CONVERT(varchar(30), GETDATE() ) AS [column3]

The CONVERT function is specific to T-SQL and is not part of the ANSI standard. Use CAST for non SQL Server data sources. ETL+ Extract SQL Statement: CONVERT()

Comments in SQL

-- 1 as [someTable]                   comments out 1 line

/*  comments out everything until closing delimiter
more comments
more comments */

Related Pages

v2023.07 ✅

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.