Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
We've an Issue (Requirement) to test ODBC config (connection to a Cloud DB) via 'File DSN' option available in 'ODBC 32/64 Bit viewer' in Qlik Windows server.
Can anyone please share the ways.
We've 'ODBC, OLEDB, QvRestConnector options available in Qvw doc. System DSN & File DSN tabs in ODBC config window/wizard. But how can we use File DSN in Qv Report.
Thanks,
Krishna Teja.
Hi @Krish-BI_Engineer ,
Thanks for the context!
About QlikView + File DSN, QlikView’s standard path is System DSN or User DSN via the Windows ODBC Administrator or a driver-based connection string. The UI doesn’t expose a “File DSN” picker. In practice, many drivers work fine from QlikView using a System DSN or a full connection string;
If your constraint is “File DSN only,” a clean workaround is to pull with PowerShell via ODBC using the FILEDSN and dump to CSV for Qlik to load.
One of the superpowers of Qlik is being able to invoke these external handlers and deliver results!
You would have to use the Execute command inside your Load Script.
How does that sound to you?
Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hi @Krish-BI_Engineer ,
I quite didn't follow, but I want to assist.
Could you elaborate on what source are you trying to connect to?
Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hello @hugo_andrade ,
Thanks for your response.
We are trying to connect SingleStore DB from Qv. However, irrespective of DS (SAS, SQL etc), we wanted to implement (Data connection) via DSN File (ODBC Connection string) instead of System or User DSN options, in Windows 2016 OS & 64 Bit platform.
I Hope the context (background Needs) are clear for you, now !
Please share your comments and the feasibility in Qlikview.
Hi @Krish-BI_Engineer ,
Thanks for the context!
About QlikView + File DSN, QlikView’s standard path is System DSN or User DSN via the Windows ODBC Administrator or a driver-based connection string. The UI doesn’t expose a “File DSN” picker. In practice, many drivers work fine from QlikView using a System DSN or a full connection string;
If your constraint is “File DSN only,” a clean workaround is to pull with PowerShell via ODBC using the FILEDSN and dump to CSV for Qlik to load.
One of the superpowers of Qlik is being able to invoke these external handlers and deliver results!
You would have to use the Execute command inside your Load Script.
How does that sound to you?
Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Thanks for sharing your ideas in this Forum.
FYI, we've tried with the existing ODBC options (System & User DSN) and Also, with 'Full connection string'- text file & direct command in Qvw doc, as the UI picker doesn't allow File DSN.
The Hunt for solving the Issue (S2 DB connectivity from On Prem Qlik server (Windows) via JWT Auth) is still open at our App side.
Please close this case/ Enquiry. Have a Nice day.