December 8, 2011 at 9:48 am
Hi
Like to know what to do when the BatchRequest/Sec reaches above 1000/Sec .
What step you taking to minimize the batchrequest.
Thanks:-)
December 8, 2011 at 9:50 am
Get less users working on that system.
Nothing you can do about that.
1 exception is if you have a massive report running 1000s of queries. Then you can change that report to run only 1-2 queries instead.
December 8, 2011 at 9:57 am
thanks for reply ,Yes we have reporting enviornment and lots of reports runnning all the time .
so how we can chane that report to run only 1-2 queries instead of 1000 queries runs same time.
December 8, 2011 at 10:01 am
Why do you want to?
What is it about 1000 batch requests/sec that troubles you?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 8, 2011 at 10:02 am
logicinside22 (12/8/2011)
thanks for reply ,Yes we have reporting enviornment and lots of reports runnning all the time .so how we can chane that report to run only 1-2 queries instead of 1000 queries runs same time.
We're going the wrong way about this. Check your biggest issue with this =>
Remember that 1 very long query is just as bad as 1 small query running 1M times in a row.
And I've heard this is a great free book (didn't read it yet)
December 8, 2011 at 11:32 am
trying to find out to minimize the batchrequest/sec .Some times it goes very high.
December 8, 2011 at 11:32 am
Thanks for kind Info very useful thank you
December 8, 2011 at 11:34 am
logicinside22 (12/8/2011)
trying to find out to minimize the batchrequest/sec .Some times it goes very high.
This counter is not useful all by itself.
100% cpu, very useful. 1000 requests sec, completely useless unless your "normal" day is 100.
I've seen sites go up to 1 Million / sec and that was on a slow day.
December 8, 2011 at 11:55 am
logicinside22 (12/8/2011)
trying to find out to minimize the batchrequest/sec .
Why?
If you want to minimise batch requests/sec there's a very easy way. Stop SQL Server. That'll drop the counter right to 0 immediately.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 8, 2011 at 11:59 am
1000 per sec is not that high for some of my servers. That measurement all by itself has little meaning.
The probability of survival is inversely proportional to the angle of arrival.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply