November 9, 2011 at 6:40 am
hi All
we will train how to use reporting services' report builder for 30 people.
and all trainee remote to the server thru the ssrs url everytime they need to build a report using the report builder(which uses report model)
it can be the same query at the same time.
the current environment is set up as forms authentication with the database on a different server
can you suggest anything that can enhance performance?
or are we ok with the current set up as long as the tables are indexed.
your valuable input...
thanks
Dani
November 9, 2011 at 6:56 am
It's difficult to say if you will face performance issues or not without knowing anything about the types of queries and the amount of data involved.
Generally speaking if the queries that are being used by reporting services are running well and the indexes on the tables are being used then you should be okay.
November 9, 2011 at 7:37 am
the queries are relatively simple ,
but these are simantic queries that report builder creating behind
or do you know how to simulate and test this with 25 users
November 9, 2011 at 7:44 am
Is this for a cube or relational source?
There is nothing inherently wrong with your setup, but there are things you can do to prepare.
I would start by looking at the query that is created by the report model and ensure it is as optimised as possible.
November 9, 2011 at 8:01 am
Best way to find out if it will perform okay or not, and is secure or not, etc., would be to open it up for use by anyone who wants to for a while. Get friends, family, people with laptops in a local Starbucks, et al, to connect to it and play with it.
Trace the activity, monitor performance stats, see how it does.
Just make sure you don't have your credit card numbers or anything like that in the database, because someone will try to hack it if you do this. If the data is set up so that it's okay, that's a good thing. It will tell you whether your system is secure or not. Then, when you actually go live with it, you can have more confidence.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 9, 2011 at 8:02 am
Talk to the people who set up SSRS for you. Ask them to help you load test this.
November 9, 2011 at 8:13 am
The set up was done inhouse, I created the models , it is not using cubes
I am thinking to create reports and schedule them to run at the same time!
November 9, 2011 at 8:18 am
If you've never done load balancing testing before, I suggest you don't schedule the reports to run simultaneously until after you've taken a baseline performance test of each individual report. Otherwise, you'll be going insane when performance takes a hit, trying to figure out which report did the deed.
Get your individual baselines, then test all reports running at the same time with a single user. Then open it up to wider and wider groups. But don't go 0 to 60 when you don't know how to do the testing.
November 10, 2011 at 9:41 am
I would agree with Brandie that you want some baselines for each report before you go larger scale.
The other thing I might check is running a load test of the queries with something like SQLIOSIM (http://support.microsoft.com/kb/231619) to test the queries on some scale. Maybe run 25-50 of the queries from reports. That won't test the SSRS server, but it will test the data piece. That will also help you to determine if it's a query issue or rendering issue under load.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply