It seems I may not have fully understood your question. Could you please elaborate on your concerns?
How to create the snapshot of full load in the target? Is there any option available?
Could you clarify what you mean by "snapshot" in this context? Additionally, what are the source and target data systems involved? Understanding these details will help us provide more accurate guidance.
How will schema changes in the source be reflected in the target? Is it only through manual specification, or are there other options?
Qlik Replicate can propagate certain schema (DDL) changes from the source to the target. However, the types of DDL operations supported vary depending on the database platforms in use. If you could specify which databases you're working with and what kind of DDL changes you're referring to, we can provide more precise recommendations.
Hope this helps.
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
To add to @john_wang 's remarks, Qlik Replicate does not capture a database backup from the source and restore it on the target. It performs a "select *" against the source tables and writes that data to the target, creating the target tables based on the DDL and constraints of the source table. One exception to this behavior is if the source has a multi-column PK defined. Qlik Replicate will use the first column alphabetically in the list of PK defined columns. You can avoid this by manually creating the tables on the target before the full load and setting the full load task settings to truncate before full load.
If the task has both full load and apply changes enabled, the default, the task will start capturing the changes occurring in the source transaction log before the full load starts and caches those changes in order to apply them to the target after the full load completes.
This description is for the most common use cases where source and target are an RDBMS and may also describe the behavior of other endpoint types - but per John's comment we need more specific details of your use case to provide specific information.
