Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

Sending notifications when DDL is detected on the source

CAH123
Contributor III
Contributor III

Sending notifications when DDL is detected on the source

Hello Team,

 

When the tables got dropped SAP Hana source, it will also dropped the triggers.  So   Attunity connectors should be alerted  and tables should be error out.    But Attunity not doing any.  

We tested this by manually dropping the table and triggger also from source. But there is no warning or error in Attunity task.

There are 200 tables got dropped  from source and again created. But Attunity task was not having any error for this tasks. After creating the tables CDC was not happening as there was trigger issue.

 

Thanks,

Tushar

Tags (2)
9 Comments
Ola_Mayer
Employee
Employee

DDL change capture is planned with our log based replication and it is already on the roadmap

Status changed to: Closed - Declined
chekurim
Contributor
Contributor

Just for clarification. Log based is the only option going forward  and that is reason DDL change captured is enabled only for Log based?. Triggered based is not recommended going forward by Qlik for HANA source end point. 

Ola_Mayer
Employee
Employee

We don't plan to to implement this feature at this time.

Our focus for enhanced feature is log based replication that is coming next year.

Status changed to: Closed - Declined
Ola_Mayer
Employee
Employee
 
Status changed to: Open - Collecting Feedback
sidneyb
Contributor III
Contributor III

The ability to detected and notify if DDL changes happened on the source is critical on enterprises that have multiple teams responsible for different parts of the end to end workflow. For instance, teams that are responsible for source systems might not be responsible for downstream systems. Typically enterprises have change management process in place, but most of time there are communication issues which impacts the end to end workflow.

If DDL changes cannot be replicated to source, at minimum Qlik Replicates need to detect and notify, and pause the replication task, so that the team responsible for the replication task can decide if the DDL changes needs to be replicated or not.

Meghann_MacDonald

Hi Everyone, 

We will continue ot leave this open for collecting feedback. Add your likes and comments to support the idea.

Meghann

sidneyb
Contributor III
Contributor III

Hello, is there any update on this feature request?

Meghann_MacDonald

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.

Ideation
Explorer II
Explorer II
 
Status changed to: Closed - Archived