Skip to main content

Suggest an Idea

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

ODBC Connector for Qlik Data Gateway

Alastair_Ometis
Partner - Contributor III
Partner - Contributor III

ODBC Connector for Qlik Data Gateway

Hi,

One feature that is obviously lacking from Qlik SaaS is the ability to connect to data sources that do not have a supported connector and are only available via ODBC.

ONe way aroudn this problem is to run Qlik Sense Enterprise on Windows (QSEoW) or Qlik Data Transfer (QDT) to connect to these sources to extract and store the required data as QVD data files and then push them to SaaS via QDT.

With the arrival of the Qlik Data Gateway (QDG) we now have support for on-prem data sources that do have a supported connector however QDT/QSEoW and QDG cannot co-exist o nthe same server so we would need to have both a server running QSEoW/QDT and a separate server running QDG if we need to connect to some on-prem data sources that have supported connectors and some that do not.

Can ODBC Data Source access via QDG be enabled preventing the need for two separate servers for this use case.

 

 

Tags (2)
40 Comments
Rudolf1
Contributor
Contributor

Good day,

I installed Qlik Data Gateway, and urgently need connectivity to our on premise database from the server where QDG is running.  The database system is:

SAP SQL Anywhere,  version 17.0

This database was previously owned and maintained by Sybase, but is now owned by SAP.

Regards

@Rudolf.visser@vanschaik.com 

Marco_Imperiale
Contributor III
Contributor III

Hi @Ola_Mayer , the problem with using database-provided ODBC connectors (MySQL for example) is that they are kept up-to-date and released faster than Qlik's. Personally I had problems with MySQL on some "Data" type fields that were not read correctly, replacing the MySQL driver the error did not occur.

Ola_Mayer
Employee
Employee

@Rudolf1 what version of the driver are you using?

AdyWorrall
Partner Ambassador
Partner Ambassador

I seem to have issues with the Qlik cloud, direct access SQL connection not allowing timestamp fields. 

I’m not able to change the data type in SQL itself to have to remove the field from my select statement. 

is that a known bug?

Ola_Mayer
Employee
Employee

@AdyWorrall what type of timestamp is it?

AdyWorrall
Partner Ambassador
Partner Ambassador

Hi @Ola_Mayer . Not quite sure what you mean - the field type in SQL is timestamp.. 

Ola_Mayer
Employee
Employee

@AdyWorrall you can find a list of all supported SQL Server datatypes here Microsoft SQL Server | Qlik Cloud Help. As you can see there can be different flavors of time datatype.

I just want to make sure that the one you are using is on this list before we open a support case.

AdyWorrall
Partner Ambassador
Partner Ambassador

Hi @Ola_Mayer - so this is the table design of a Sage 200 table - it is the fields that have type of 'timestamp' that the connector will not allow. 

 

AdyWorrall_1-1673626265869.png

 

 

AdyWorrall
Partner Ambassador
Partner Ambassador

ps @Ola_Mayer  - that field type is not listed in the link you provided - thank you for the help on this

AdyWorrall
Partner Ambassador
Partner Ambassador

Hi @Ola_Mayer  - i know this isn't the correct thread, but do you know where I go to ask if a connector can be added to Qlik automation for ClickUp please?