Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.

In this case we have a mix. We have summarized data on some decks and details on other decks, because the customer need to look at details that are related to.  We have advised the client that in an executive report type the detail should be shown in a separate report, but they say it's more convenient to have it in the same report.

Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.

In this case we have a mix. We have summarized data on some decks and details on other decks, because the customer need to look at details that are related to.  We have advised the client that in an executive report type the detail should be shown in a separate report, but they say it's more convenient to have it in the same report.

Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.

In this case we have a mix. We have summarized data on some decks and details on other decks, because the customer need to look at details that are related to.  We have advised the client that in an executive report type the detail should be shown in a separate report, but they say it's more convenient to have it in the same report.

Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.

In this case we have a mix. We have summarized data on some decks and details on other decks, because the customer need to look at details that are related to.  We have advised the client that in an executive report type the detail should be shown in a separate report, but they say it's more convenient to have it in the same report.

Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.

Ok, those are both below 10Mb, so should be fine in use. The fact one is taking two minutes to render and the other is taking an hour is likely due to the volume of rows having to be aggregated in Dev vs Production. One thing you could try is grabbing the SQL the report is generating and running this directly against the underlying databases to see how long the query takes to execute in Dev vs Production?

Cheers!

MF.

In this case we have a mix. We have summarized data on some decks and details on other decks, because the customer need to look at details that are related to.  We have advised the client that in an executive report type the detail should be shown in a separate report, but they say it's more convenient to have it in the same report.

Hi,

I would recommend you try to stick to an overall size of 10Mb or less for a rendered active report output. Often your output will contain summarized data, so although your Dev and Production environments might be generating outputs of similar size (for example 1,000 rows in the output), it's entirely possible your Dev environment might be summarizing thousands of underlying rows to produce the 1000, whereas the Production environment might be summarizing hundreds of millions of rows to produce the 1000. Is this the case?

Cheers!

MF.