I have created a connection and generate a cache for small qvw (5MB) without any problems.
Larger files (approx 800MB) are taken longer as expected.
I have only 1 engine.
Is anyone using nprinting with large documents or
is it better to create documents specifically to use with nprinting (I'd rather not do this).
I use very large documents with my NPrinting. One is 12 GB in size. I will give you my opinion based on my experience which may or may not be considered best practice. We are still using ver 16, so if you are on 17, this may be different.
I think the frequency that you are updating your data can determine the answer to your question. We only update our data once a month, so we choose to have a static QVW file that we copy and use for Nprinting purposes only. If you update daily or more often, this might not be a practical step
This also enables us to use several schedules for printing. I can use the server and have it read its own QVW and I can also use a client or two to run schedules locally. This divides my load. We have several people that use NPrinting clients for development and just have the QVWs loaded on a local drive.
I would say the optimal best practice would probably be to read the QVW's directly from your QV server. You will have to do some experimenting and see what works best for your scenario.
Not sure I answered your question but hope I gave you some perspective.
I just read your other post and see that you have the trial to 17. Are you still using 16 or are you starting with 17? Likely most of what I just told you will be more geared towards 16
Thanks for the reply Mike.
Always good to hear the way other people work.
We don't have nprinting yet, I did have a trial for version 16 in Feb 2015 but we couldn't really justify the costs.
At the moment, we have more and more excel reports that need to be created on a daily basis.
I would look in your data governance dashboard and see how often your users are exporting data out to Excel. It should be pretty easy to put together a cost justification if you are saving the labor of the everyday tasks.
Perhaps you could justify starting with the SMB version and upgrading after proving cost ROI.
Check with your partner on pricing options.
So far I have been able to generate a cache for a 200MB without a problem.
No joy with the 700MB qvw, I have logged a case with Qlik Support.
Did you get a response from Qlik? Just wondering what the file size limit would be as we've now got this problem with NPrinting 126.96.36.199.
It is able to generate cache for smaller files but not larger ones (> 600mb)
Sorry for delay, I've been out of the country for the past week in Ireland.
I logged it with support and they suggested I wait for the new release that was coming out soon at that time.
I couldn't wait so I had to go with version 16 instead.
I would log the problem with Qlik Support.