June 21, 2011 at 2:31 am
Hi All
System Info...
Server. 12G RAM, 2xQuad Core processors. Hard Drive C (RAID 1), Hard Drive E (RAID 10). 1G NIC
SQL Server 2008 R2. All system DBs on Drive C. 1 User DB, with Log file on Drive C and Data file on Drive E.
The application is Dynamics AX 2009 😉
I have a report which is taking > 30mins to execute! I started the Activity Monitor and notices that the batch request/sec was about 1500-2000! with low CPU utilisation. Looking at task manager, the Network adapter (1Gb) was being utilised ~3%.
For who is not familiar with AX, the report is prossed on the AOS server (another server) and this server talks with the DB server. A lot of SQL statements are executed on the DB server and the results sent back to the AOS server which eventually will send the report back to the client.
I started suspecting the the DB server is not being fully utilised due to the low CPU utilisation and since the batch request/sec is low, it's not being hit hard enough by the AOS server. For a Gbit NIC, what network utilisation should I expect? Is there any guideline?
Regards
Brian
Regards
Brian Ellul
----------------------------------------------------------------------------------
Computers are incredibly fast, accurate, and stupid. Human beings are incredibly slow, inaccurate, and brilliant. Together they are powerful beyond imagination.
- Albert Einstein -
June 21, 2011 at 3:53 am
Have you looked at disk queue or memory paging?
May 2, 2013 at 2:48 pm
I have SQL server 2008 running on a Dell Server with 8 processors and 24 Gb RAM. Every few weeks the third party applications receives an SQL timeout issues which freezes other users. I then have to restart the server to bring it back on line. I have been running PerfMon and notice that my batch requests/sec were on average less than 10. My database is only 160 Mg and at most 25-30 user connections. Processor usage is minimal. Page life expetancy is over 300. Page splits are at time double the batch request/sec. Other performance parameters seem ok. Network connection readings are good. I set the memory max of 20 Gb and concurrent connections to 100.
Why would the system timeout? Could this be an issue regarding the programmin?
May 2, 2013 at 3:14 pm
rsorrentino (5/2/2013)
I have SQL server 2008 running on a Dell Server with 8 processors and 24 Gb RAM. Every few weeks the third party applications receives an SQL timeout issues which freezes other users. I then have to restart the server to bring it back on line. I have been running PerfMon and notice that my batch requests/sec were on average less than 10. My database is only 160 Mg and at most 25-30 user connections. Processor usage is minimal. Page life expetancy is over 300. Page splits are at time double the batch request/sec. Other performance parameters seem ok. Network connection readings are good. I set the memory max of 20 Gb and concurrent connections to 100.Why would the system timeout? Could this be an issue regarding the programmin?
Why do you need to configure concurrent connection setting to 100. ??
By default it will be 0 and better to leave as it is as SQL server will allow up to 32000 and more connections.
May 3, 2013 at 7:35 am
THe most user connecting to the server would be less than 100. I understood the limitation of changing it. My dilemma is having to restart the server every few weeks and I have been checking all the readings in perfmon. I can't tell if the server is the issue or the programming?
May 13, 2013 at 7:30 am
Like i stated, the batch requests / sec is very low. Less than 10. I have checked all network, memory, and cpu readings and they appear to be ok. What else could be a server issue before I go to my programmer to rewrite some of his applications?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply