Reloading without distribution

[fredericvillemi]

Hello,

I'm quite new to using Publisher after years of Qlikview Server only.

I have transferred all refreshes to Publisher but sometimes I don't need any Distribute because I'm just creating QVD.

I can't find where, in the task interface, I could only refresh a document in Publisher without distributing or reducing it .. Is it possible ?

Even some documents take a long time to refresh and again after the refresh is done, they spend time to distribute .. but i dont want to have this distribute

How can I do to have only Publisher reload documents without distributing them ?

Thanks

[zhadrakas · Accepted solution]

just leave everything blank in Tabs "Reduce" and "Distribute"

Just Set the Trigger and you are fine.

[Peter_Cammaert]

Reload, Reduce and Distribute are different stages of a task. Each one requires a reload engine to open the source document, do something with it and save/distribute it to the same or a temporary document, or to the QVS. For large documents, each one may take a lot of time to finish. And may create queues when not enough engines are available at the same time.

Do as Tim said. Disable the Reduce and Distribute phases on the respective tabs, enable the reload tab and define a trigger. To get even better performance, wipe the data model at the end of the script in your QVD Generators.

[YoussefBelloum]

Hi,

just don't add users or groups here

[fredericvillemi]

Thanks for all your answers

They should add a checkbox for every part of the reload / reduce / distribute

[pat_agen]

Hi,

am looking for a variant on this answer.

I have a Publisher chain of tasks. The last task creates and then distributes a qvw. However in certain circumstances (for example no change to data in the qvw) I do not want the qvw to be distributed.

Any idea on how to make the distribution task conditional?

I don't want to purposefully create an unsuccessful event as this will create confusion for monitoring.

[Reason: since migrating to v12 users have seen a degradation in performance when a document on which they are working is refreshed, - the "graceful refresh" does not seem to be as graceful as previously]

[bnichol]

Hi,

Did you ever find out how to make the make the distribution portion of a task conditional? 

I have a dataset that can sometimes have no entries, which causes the load to fail.  I could put in a condition to handle the error, but then I would be publishing an empty application.  I would like to handle the exception, but not distribute the reloaded application.

Any ideas?

[Maria_Halley]

@bnichol 

I am not sure I understand the question correctly, but if the reload itself fails, the document should not be distributed. 

The distributions are only done after a successful reload