Connecting to an Azure SQL Database from Data Movement Gateway
Have anyone got this working? We can connect from the Gateway VM, but when trying to connect from Qlik Data Integration (creating a connection) we only get timeouts. The GW VM is whitelisted for traffic on 1433 in Azure. We are using user/password as credentials (only way).
Stefan is this a target for data replication scenario only, or a target for pipelines (landing, storage, transformations).
If the former, please make sure you set the gateway in the definition for the target. If the later you can do the same as above, or please ensure QLik Cloud has access to your SQLDB.
So, what you're saying is if the DI project is Data Replication, then the data will move from Gateway to target, and if the DI project is Data Pipeline, then the data warehousing will be accessed from Qlik Cloud to target?
Is there a difference between connectors here, or is this always the "split" in behavior between Replication vs Pipeline projects?
Hi Stefan, no , sorry for not being descriptive enough.
For RDMBS / SAP / Mainframe (e.g. not SaaS applications), the data path is SOURCE-> GATEWAY-> TARGET. Data does not pass through Qlik Cloud. For SaaS application, the path is currently SAAS APPLICATION->QlikCloud- > Gateway -> Target as the capture / parsing of the JSON payload is performed in the cloud.
There are multiple possible connection points to your target when you create a connection. The gateway for data movement, but if you are using data pipelines (landing/storage/transformations) then Qlik Cloud could also be a connection point for orchestrating pushdown SQL for transformations. So when you create a target connection without a gateway defined, we test from Qlik Cloud.
Defining a gateway in the target connection is used for the test connection, but it also allows that gateway to orchestrate ELT commands when Qlik Cloud cannot connect to your target. (eg. for you if you were to perform pushdown SQL for SQLDB, then you can have teh db-commands service in the gateway perform that orchestration without having to open the firewall to Qlik Cloud.
When a target connection is created and a gateway is assigned it
- Forces test connection to use the gateway
- Forces ELT commands to use the gateway
- Data Movement tasks still run where the source connection is defined (in the event you have multiple gateways in your environment the source connection takes precedence for the execution of the movement task)
