Alternatives for VIEW DATA STATE in Azure SQL repl… – Qlik Community

admin

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 – community.qlik.com/t5/Qlik-Replicate/Full-Load-Only-Permissions-for-MSSQL-Source/td-p/193819… )

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.

Read more here: Source link