# Using passthrough mode on SAS studio (for SAS/ACCESS interface to JDBC)

**URL:** <https://community.cdata.com/t/using-passthrough-mode-on-sas-studio-for-sas-access-interface-to-jdbc/423>\
**Category:** Data Sources\
**Tags:** article, jdbc, sas, sas-viya, sas-access\
**Created:** [September 26, 2023, 8:24pm UTC](https://community.cdata.com/t/using-passthrough-mode-on-sas-studio-for-sas-access-interface-to-jdbc/423 "2023-09-26T20:24:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dardi\_R](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@Dardi\_R](https://community.cdata.com/u/Dardi_R)\
**Post date:** [September 26, 2023, 8:25pm UTC](https://community.cdata.com/t/using-passthrough-mode-on-sas-studio-for-sas-access-interface-to-jdbc/423/1 "2023-09-26T20:25:17Z")

</div>

SAS Studio environment can use any JDBC data source thanks to its JDBC interface. On previous issues we have monitored a certain query modification done by the tool or the SAS/ACCESS interface resulting in badly formatted queries, throwing both server and driver errors.

On these occasions using the following code to connect and query enables a ‘’passthrough mode” which preserves the query from any modification done by SAS platform.

Example:

proc sql;

CONNECT TO JDBC as conn (classpath=“/Public/Drivers/cdata.jdbc.databricks.jar”

class=“cdata.jdbc.databricks.DatabricksDriver”

schema=\<databricks\_schema\>

URL="jdbc:Databricks:Server=\<your\_server\>;

HTTPPath=\<yourhttppath\>;

AuthScheme=PersonalAccessToken;Token=\<your\_token\>");

Select \* from connection to conn (Create table test1 (Name Varchar(10)));

disconnect from conn;

quit;

Additional details can be found on the following documentation:

- [SAS Help Center: SQL Pass-Through Facility Specifics for JDBC](https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/acreldb/n0vim8t3myw37xn1y1u5t9dzz2ll.htm)