Instead of using parameters, base your security decisions

Execute reports from cached/snapshot data as opposed to live data whenever possible. Limit non-essential background processing to off-peak hours in order to avoid contention with online users. If you load your report server up with 4GB memory, remember to set the /3GB switch in C:boot.ini so application processes can make use of it. If a single server can t handle the workload, consider locating the Reporting Services catalog on a remote SQL Server instance as your first step toward increasing system capacity. If one report server configured with a remote catalog still doesn t adequately support your workload, consider increasing the available resources on the system hosting your report server (scale-up), or setting up a clustered Web farm of report servers (scale-out). 374 Part VII: The Part of Tens

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost JSP Web Hosting services

Bookmark the permalink.

Comments are closed.