While using the SrsReportDataProviderPreProcess class as RDP, use the Regular table to insert data in the reporting table. Also, set the CreatedTransactionId property to Yes.

Use TempDB tables when dealing with a large amount of data.

Use Extended Data Types (EDT) for the temp table fields so that the labels and other properties would be automatically handled by the report framework when the report is rendered.

Provide proper labels to the fields, in case EDT is not used for a field.

Provide proper indexes.

Provide table relations to the foreign key fields, to enable Auto links to the report. It helps to drill-through to the master form.

Use the TempDB or InMemory table as the reporting table while using the SrsReportDataProviderPreProcess class as RDP

Use the Regular table when extending to SrsReportDataProviderBase

When dealing with a complex query involving multiple joins, use the RDP class to insert data into the temp table and render data onto the report.

When dealing with a large amount of data, use the SrsReportDataProviderPreProcess class.

Use a user connection at the beginning of the processReport() method while using the SrsReportDataProviderPreProcess class as RDP.

Perform database related functions to be executed on the server only.

Use the processReport() method to process business logic. Also, set SysEntryPointAttribute at the beginning of processReport().

Use RDP if a dataset can be generated by a query

Use client based operations like printing information, warnings, or errors

Use the contract class to add parameters to the report

Perform a validation to check if all parameters have correct values, or to check the mandate parameters

Provide labels if they can come from EDT

While dealing with multiple designs, use the controller class

Use the controller class to modify contracts

Process business logic in the controller class

Send the dataset to the RDP class

Use the UI Builder class when a specific UI is required to be rendered before the report generation.

Use the build method to add all dialog fields to the report dialog.

Use the postRun() method to override dialog fields behavior. For example, providing lookups and modified events

Modify contracts in the UI Builder class

Control visibility of parameters in the UI Builder class

Use templates for designing reports to provide a report presentation across the system

Use labels in Caption and Description properties for report controls

Use Auto Design for all simple reports

Use a proper report name, so that it can be easily referred back in AOT

Use Auto Design for form based reports like Invoice or Confirmation reports, where a field's position has to be set to a value, instead of Auto

Include a report design in the report which is not used

Provide a field list while creating a query, so that only required field values are selected

Provide proper relations when joining data sources

Use Query directly in a report which has multiple joins and grouping, instead use the RDP class