Qlik Cloud Data Integration (QCDI) enables data integration teams to build data integration pipelines rapidly using software automation that leverages an Extract, Load, and Transform (ELT) design pattern. A central feature of the ELT design pattern is pushdown SQL, where the transformation code generated automatically by the QCDI solution is “pushed down” to be executed on the cloud data warehouse platform, where the extreme scalability of such platforms can be leveraged fully.
One often-overlooked aspect of generating transformation code using QCDI automation is that it requires the QCDI solution to create and manage the schemas and tables against which it will execute the SQL code it generates.
While efficient and extensible, the ELT-based QCDI pipeline automation solution will create multiple schemas, tables, and views. A table that summarizes the schemas, tables, and views created by QCDI object type is included at the end of the paper. The body of this paper is devoted to describing the objects the QCDI pipeline automation creates, and their purpose, to allow your system administrators to better understand the implications to the physical database layer.
Environment
Qlik Cloud Data Integration
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
