Writeback Storage

[Crichter141]

Referencing the Creating a Writeback solution video here:  https://community.qlik.com/t5/Product-Innovation/Creating-a-write-back-solution-with-Qlik-Cloud-is-n...

I am following just fine until the MS SQL piece.  I feel really dumb and like I should see the answer.  But I'm trying to keep the traffic back to the data warehouse to a minimum (costs).  Is there a way to update back to the QVD that exists already in the Cloud?

Second question, what does the partial reload - in reference to the writeback- do?  Is it only reloading the updated record?  Or does it reload all the related QVDs for the table that record exists in?

Thanks for letting me ask.

[Crichter141 · Accepted solution]

Just to provide an update, once we've moved to the Cloud we have moved away from writebacks to our data warehouse and instead are writing back to a QVD in the Cloud.  Closing the loop.

[Congrid]

Hi @Crichter141 ,

Could you share on how you are writing back to the QVD in the cloud? 

Is the QVD stored in DataFiles or a cloud storage?

[Crichter141]

Hello!  Certainly.  It is in the Datafiles as a QVD.  We used to pass everything back and through to our data warehouse on prem, but found it more economical (and responsive) in cloud to utilize the datafiles.  I hope that helps.

[NS_Qlikupdates]

If you're trying to write back from Qlik Cloud to your on-prem SQL Server, the SenseOps Writeback extension can help.

Qlik’s Data Gateway is read-only, which is why your Automation flow fails with the login timeout. SenseOps bypasses that limitation by using its own secure writeback service that connects directly to your on-prem SQL Server.

It lets users edit or add data inside Qlik Sense and reliably saves it to SQL, without needing Qlik Automations or exposing your DB to the cloud. Know more