November 25, 2009 at 9:34 am
Hello,
Our busyest PeopleSoft Application with over 300 users is running super slow all of sudden.
We have a page that searches for Field Orders. Normally, this search take about 5 seconds. On a bad day it takes about 20 seconds. Now it is taking over a minute!:w00t:
The system has 2 boxes.
box 1 has the application server, and web server
box 2 has sql server 2005 with SAN drives, 16 processors, 64 GB RAM
On box 2, we noticed yesterday that under the task manager/processes tab, sqlservr.exe is only using around 306,260K memory! In SQL Server we have set 55GB memory. On other similiar sql db boxes the sqlservr.exe service is using the entire memory allowed.
We have tried restarting the sqlservr.exe server and restarting the entire box. This did not help.
Besides Microsoft server updates during the weekend, we have not made any changes to this server.
I have attached a few screen shot of task manager.
thank for any help!
November 25, 2009 at 9:38 am
Look at the performance monitor for the Memory SQL Server is utilizing.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 25, 2009 at 9:49 am
Run this query and post what's the values returned.
select * from master.dbo.sysperfinfo where counter_name LIKE '%Memory%'
and [object_name] like '%SQLServer:Memory Manager%'
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 25, 2009 at 9:53 am
November 25, 2009 at 10:10 am
Task Manager does not always show the correct memory usage of SQL Server.
The results show that SQL Server is using the 55 odd Gigs you have configured it to.
Any clue on what else is the cause for your sudden slowness?
Any thing has been changes on the server, database any option being modified or changed?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 25, 2009 at 10:31 am
We really never change any settings on the DB.
2 weeks ago, the snap manager (san drive stuff) software was updated. Then last weekend Microsoft server updates were installed.
We are considering opening a case with microsoft, howerver, they are very slow to respond. We may end up rebuilding this server. 🙁
thanks for your help
November 25, 2009 at 10:33 am
Bru,
From the screen shots that I have posted, would you agree that something looks wrong with the amount of memory being used?
November 25, 2009 at 10:34 am
Orange Crusher (11/25/2009)
We may end up rebuilding this server. 🙁thanks for your help
Rebuilding the server ? Just because a query being slow ?
Were you already in the path of rebuilding the servers for some other reason?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 25, 2009 at 3:37 pm
We are working with MS support. Support agrees that there is a problem with the memory and they are looking at our logs
November 25, 2009 at 3:47 pm
Post here when you have an update.
Happy Thanksgiving
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 25, 2009 at 7:10 pm
Curious. A few things if I may ask, can you provide details regarding your server configuration (memory, processors, x64 or x32 (I'm assuming x64), OS and version, SQL Server and build), wether the servers are blade servers or not. What type of connection to the SAN and how the databases are placed.
Also, what version of PeopleSoft (Application and Tools) are you running.
Here's why:
We are currently running PeopleSoft HR (9.0) and Finance (8.9) and I believe we are on Tools Release 8.48. We are running on x32 hardware and using SQL Server 2005 SP 2 (no CU's).
We are planning a migration to x64 Blade servers along with a move to Tools version 8.5x and upgrading to SQL Server 2008 SP 1. Yes, everything on the PeopleSoft side is going x64.
Once we have the Tools upgrade completed and have moved both HR and Finance to the blades, we will then begin an application upgrade on Finance to 9.1.
November 25, 2009 at 7:15 pm
Looking at this:
We have a page that searches for Field Orders. Normally, this search take about 5 seconds. On a bad day it takes about 20 seconds. Now it is taking over a minute!
Sort of reminds me of an issue we had with PO's after upgrading Finance from SQL Server 2000 to SQL Server 2005. When our PeopleSoft Admin finally ran a trace using the PeopleSoft tools we discovered a table that was used that had no indexes defined. Under SQL Server 2000, everything worked great, but it was literally timing out under SQL Server 2005. Identifed the appropriate index, applied it, and everything was great. Have you tried doing that to help identify the problem? By the why, I had tried server side traces and profiler, the Database Tuning Advisor, and nothing from those really helped.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply