Hi @Venkatesh Gunda ,
- At first, you need to understand how long it takes to process reports and other usage metrics. You can capture data through ExecutionLog3 and see if the report is taking a long time in TimeDataRetrieval, TimeProcessing or TimeRendering. see more: Log Fields (ExecutionLog3). For performance issues at each stage, please refer to: Troubleshooting Reporting Services Performance Issues.
- Report processing and rendering are memory intensive operations. When possible, choose a computer that has a lot of memory. For more information about how to mitigate performance issues by tuning memory management configuration settings, see Configure Available Memory for Report Server Applications.
- Hosting the report server and the report server database on separate computers tends to provide better performance than hosting both on a single high-end computer.
- If all reports are processing slowly, consider a scale-out deployment where multiple report server instances support a single report server database. For best results, use load balancing software to distribute requests evenly across the deployment.
- If a single report is processing slowly, tune report dataset queries if the report must run on demand. You might also consider using shared datasets that you can cache, caching the report, or running the report as a snapshot.
For more information, please refer to: SQL Server Reporting Services Best Practices for Performance and Maintenance.
Best Regards,
Joy
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.