Best Practices on User Limitation of Report Server Accessing

  • Please recommend the Best Practices on User Limitation of Report Server Accessing such as how many users can access report at same time, if more number of users access at same time what is the resolution

  • From the description, I'm thinking the issue is you have a slow report,and if multiple people hit it, it's slow, bogs down the system, etc.

    I don't think there is a best practice for limiting access. That's the opposite of what the best practice would be.
    The best practice would be tuning the report, or caching it /snapshot it to a table so it is faster. I can imagine a report with 20 or more joins , and a crappy design with twenty optional parameters, for example being painfully slow, for example.
    if there is a business need that 100 people hit the report at the same time, we don't limit access; we tune the report so it produces data in the fastest way possible.

    What, specifically is the issue?

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Looking at Scale-out best practices

  • SQLCAT had several articles related to this - they moved those into an eBook. Check section 5 in the BI and Analytics ebook which you can download from here:
    SQLCAT.com ebook Downloads

    You can still get the slides from an older TechEd session - much of which still applies, has good content. You can download those from the Channel 9 site:
    Scale-Out Deployment of Microsoft SQL Server Reporting Services

    Sue

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply