Running report performance (memory exception and slow generation)

Capone

Hi!
Perhaps the header is a bit misleading. I'm not after on how to create a low performance report but I'm more interested how the generation/creation of the dataset works.

We have customer that has a lot of invoices and that has the following issues.

First: When they try to do the invoicing and print all the documents they get the out of memory exception.
Now we talk about a couple of hundred invoices. I have already redesign the dataset so logo is only included in the dataset once.
The first thing we are going to do is to create function that only prints the invoices by one hundred a time and that will be a workaround.

The user tried to do the printing both on his local crappy computer and on the citrix server. The interesting thing on the citrix server is that the report doesn't really affect the total available memory meaning it gives the exception even though it looks there are plenty of memory.
Are there somewhere a property on how much memory a report can access? Or is it possible that the citrix has a property on how much memory a user can use?

Second:
One thing we have noticed is that the local users have a way more quicker report running than users that are located geographic else where. All of them are connected through the same citrix. Is this because the dataset is being generated on the NAV server and after that is transmitted to the local user which then pass the information along to the local printer?
Is the solution to increase the network performance between the offices or could it be something else?

davmac1

when you the report on the client, the dataset size is limited to 2GB. Maybe you can see if you can reduce the number of fields being sent to the dataset and also only send the company information fields once like the logo.
The generated dataset is send to the client - so this is why it is slow over slow connections. You could run the reports on the server and send them to a reports directory.

mdPartnerNL

The dataset is send to the client and shown by the report viewer. You can push to "show" it on the server by saving resulting report to pdf.

davmac1

when you the report on the client, the dataset size is limited to 2GB. Maybe you can see if you can reduce the number of fields being sent to the dataset and also only send the company information fields once like the logo.
The generated dataset is send to the client - so this is why it is slow over slow connections. You could run the reports on the server and send them to a reports directory.

Capone

I don't understand your answer. Aren't the report always run on the server and then transfer the result to the client?
What do you mean with running them on a server and send them to a reports directory?

mdPartnerNL

The dataset is send to the client and shown by the report viewer. You can push to "show" it on the server by saving resulting report to pdf.

davmac1

The dataset is sent to the client. Large datasets over a slow connection will take a long time to transmit. If you avoid sending the dataset to the client, the user can then view the pdf when it has been completed.