SQL Data Query

many of our business customers solve their one off data sharing needs by using a simple sql data query connection a sql data query connection allows a sql query to query data from their source system, such as a cloud data warehouse database and send the results of that data set somewhere else such as via sftp as part of their integration workflow it is as easy as it sounds create sql query against a known data source such as your database table(s), joins are allowed, etc then take the proven query and enter it in the sql query field of the sql data query this now becomes a sql data query connector that is based one of our existing cloud data warehouse connectors (other application systems such as netsuite suiteql are possible), and it can then be added as a source in your sync bridge to load to your target destination of choice, i e cloud data warehouse, sftp prerequisites you need to make sure that you have a source connector already created for your cloud data warehouse sql data query connector needs a source from which to query this is done by selecting the source in question in the new sql data query source connection form without an existing cloud data warehouse connection (e g snowflake source conector) you will not be able to use this connector you have an existing working query that you've validated returns results/records you understand that sql data query results can be limited based on your current subscription plan the lower plan(s) are limited and controlled to allow a maximum of 100,000 results/records based on any one query only one sql query per sql data query connector are allowed otherwise your connector is likely to result in failure cte's are permissable setup instructions using the source connector form please complete the following basic steps enter a name or alias for this connection, in the name/alias field, that is unique from other connectors enter in the target schema prefix field, a name that will be unique in your data cloud destination where you wish to land the data select from the source cloud database dropdown, a source connection you've previously created from which this query will be executed if you do not yet have a source connector to a cloud data warehouse you must create one before this connector can be create enter the output file name for what the target result of this query will be referrenced as when it is used by the target system, which can differ slightly depending on the target connection is aligned with in a sync bridge for example jinja usage basic jinja can be used for timestamp logic in the folder path to determine what the dynamic structure of the s3 bucket might be, for example as a time based solution, if looking in a folder prefix/bucket as such, 2025/11/10/myfiles/otherfiles/, and the date structure is correctly used over time, then the following jinja expression can be used in the folder path field, {{ today() | format date('yyyy') }}/{{ today() | format date('mm') }}/ , to ensure that dlh io is dynamically retrieving from that folder each day enter in the sql query field the sql code which you have previously validated click save & test to save the connector