Alternatives for VIEW DATA STATE in Azure SQL replication

Derek978 — Tue, 27 Aug 2024 16:20:54 GMT

Based on a number of questions and answers on these forums - for Azure SQL Server and full replication it appears that db_datareader and VIEW DATABASE STATE are required for automated implementation - does QLIK offer any alternatives to this where a custom ETL pipeline between Azure Source and Snowflake Destination can be done?

(reference - https://community.qlik.com/t5/Qlik-Replicate/Full-Load-Only-Permissions-for-MSSQL-Source/td-p/1938193 )

Things like -
* manual DDL definition of source
* SQL to define source data
* manual conversation of data types to destination

We are in a security position where we do not want to grant DB level STATE reading, but would like the ability for a vendor to be able to still use QLIK for replication.

Re: Alternatives for VIEW DATA STATE in Azure SQL replication

OritA — Thu, 29 Aug 2024 07:47:51 GMT

Hi,

The required permission for every endpoint are listed in the Replicate users guide. Apart of what is listed in the documentation, there is not other option or alternative. If you have any special request you can open an ideation request in the support portal.

Regards,

Orit

topic Re: Alternatives for VIEW DATA STATE in Azure SQL replication in Qlik Replicate

Alternatives for VIEW DATA STATE in Azure SQL replication

Re: Alternatives for VIEW DATA STATE in Azure SQL replication