August 3, 2008 at 10:06 pm
I have SQL Server 2005 64 bit on a win 2003 64 bit system. We have separate jobs which load data from the databases. We run these tasks as separate jobs for each provider for each day of listings (12,000 x 14) and each job is launched by a thread in a thread pool managed by a Windows service.
when we increase the thread pool size beyond a particular point, we start to see some performance counters (such as page reads/second) go into bad ranges and we do see lots of PAGEIOLATCH_SH and PAGEIOLATCH_UP. Where is the bottle neck?
Any suggestion on this !!!
Thanks in advance !!!
"More Green More Oxygen !! Plant a tree today"
August 4, 2008 at 9:51 am
Please find the query which pulls data from the DB and push it to file.
Is there any thing You can help me out to tune it.
Thanks fopr the help !!
"More Green More Oxygen !! Plant a tree today"
August 4, 2008 at 1:48 pm
Because of the nature of the query, a lot of what it does will depend on the content of the database when it's run. I don't see any way to do any real testing on this query without the underlying databases.
You might need to hire a contractor to come in and look at it on-site.
- 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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply