This sample is an example that illustrates how to boost performance on RTC reports. This applies to reports that are printing confined record sets (normally anything under several thousands). The attached object shows how to correctly structure the report, where possible, so as to avoid sending any records that will not show at the print/preview on RTC.
This topic describes the relationship between basic database functions in C/AL and SQL statements.
When you write a query that searches through a subset of the records in a table, you need to be careful when you define the keys both in the table and in the query so that Microsoft Dynamics NAV can quickly identify this subset. For example, the entries for a specific customer will usually be a small subset of a table containing entries for all the customers.
There are a few key performance troubleshooting techniques that are effective in identifying the bottlenecks in the performance of the database.
With the delivery of the 3-tier architecture in Microsoft Dynamics NAV then it has opened up the possibility of developing applications utilising the NAV 2009 middle tier web services.
As we have seen already in some cases, some reports which were optimised for the Classic Client may run slowly on RTC. This is especially the case when a report involves a lot of data.
Some of you might have run into scenarios that a report that runs for some (acceptable) time on classic client takes far longer time on RTC or simply even errors out with OutOfMemory kind of exception.
Vertalen
