-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAS integration #415
Comments
any solution? We faced the same issue. May be any temporary solution for make it work? |
The problem is that SAS (or another tool) does |
@bkuspayev, what driver version do you use? The latest version generates a random session id for connections https://github.com/ClickHouse/clickhouse-odbc/releases/tag/v1.2.1.20220905 |
@mshustov thank you for quick response, I'm using the exact same version as you mentioned: v1.2.1.20220905 |
@bkuspayev do you specify a session name manually? https://github.com/ClickHouse/clickhouse-odbc/pull/398/files#diff-bf39b744552791b8ebec2bcfdab832d997df90796ebf432e5c5fb13ce903df1bR118 |
I'm not familiar with the internal workings of SAS and its session naming conventions. I haven't made any manual modifications on my end. Here are the parameters from the ODBC ini file: [Clickhouse] Let me know if you need further information. |
SAS: 9.4 M7
Clickhouse: 22.3.9.19
Clickhouse ODBC driver: 1.2.1.20220905 running on RedHat 8
We are trying to connect SAS to Clickhouse database to explore data in SAS. We noticed that for every query we run in SAS there are two queries coming to ClickHouse database:
Example for small table (5 rows) from clickhouse-server.log:
How to disable this first query (SELECT * FROM table) because it breaks on bigger tables:
Driver error log:
and it slows everything down even if it succeeds.
The text was updated successfully, but these errors were encountered: