Doubt on PT

Question

Doubt on PT

Joy Smith San

SSC-Insane

Points: 24877
More actions
April 22, 2010 at 4:10 am

#139878

Dear All,
One of our client was complaining that their application has become too slow now.
It used to be fast enough. I went there and checked the server.
Following are the details.
Windows server 2003 - 32 bit.
SQL Server 2005 - 32 bit with SP2.
There are 2 CPUs.
16 GB RAM.
AWE was NOT configured.
I also found that one of their printing application (It's essential) runs and it eats upto 95% of CPU.
One EXE "sqlsrver.exe" was running and it takes 1.7GB of memory.
I have 2 questions.
1.In such a scenario, What are the things that I can do to improve performance ?
2.What's that "sqlsrver.exe" which was running and takes 1.7GB of memory ?
Thanks in advance.
Smith San.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Grant Fritchey SSC Guru Points: 398909 More actions · Answer 1

Joy Smith San (4/22/2010)
Dear All,
One of our client was complaining that their application has become too slow now.
It used to be fast enough. I went there and checked the server.
Following are the details.
Windows server 2003 - 32 bit.
SQL Server 2005 - 32 bit with SP2.
There are 2 CPUs.
16 GB RAM.
AWE was NOT configured.
I also found that one of their printing application (It's essential) runs and it eats upto 95% of CPU.
One EXE "sqlsrver.exe" was running and it takes 1.7GB of memory.
I have 2 questions.
1.In such a scenario, What are the things that I can do to improve performance ?
2.What's that "sqlsrver.exe" which was running and takes 1.7GB of memory ?
Thanks in advance.
Smith San.

The executable is SQL Server.

Without more information, it's hard to say what might be causing performance issues, although that printing application running on the same instance as SQL Server could sure be the cause. I'd suggest, as a start point, that the print service get moved to a different machine or SQL Server get moved to a different machine. It doesn't sound like they play well together.

To really understand performance issues, you need to gather more metrics. Do a search around. There are lots of lists of those metrics available.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Joy Smith San SSC-Insane Points: 24877 More actions · Answer 2

Thanks for the quick response.

The executable is SQL Server.

But for SQL Server 2005 the executable is "SQLWB.EXE" no ?

To really understand performance issues, you need to gather more metrics. Do a search around. There are lots of lists of those metrics available.

Can you please mentione a few, so that I can make sure that am on right direction...

Grant Fritchey SSC Guru Points: 398909 More actions · Answer 3

Joy Smith San (4/22/2010)
Thanks for the quick response.
The executable is SQL Server.
But for SQL Server 2005 the executable is "SQLWB.EXE" no ?
To really understand performance issues, you need to gather more metrics. Do a search around. There are lots of lists of those metrics available.
Can you please mentione a few, so that I can make sure that am on right direction...

I'm pretty sure that's SQL Server running.

There are lots of counters, but if you really want to start monitoring SQL Server, take a look at this white paper from Microsoft.

Some of the stuff you should look at is the page life expectancy to understand if memory is under pressure, cpu usage is good to see if the cpu us under pressure, which yours seems to be. You'll want to look at the disk queue length to understand if there is pressure on the disk. Those are just the basics. There's lots more that will tell you more information in detail. Focus on the wait states and queues. That's where things are slowing down, always. Once you identify what's going slow, then, of course, you have to figure out what to do about it.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Lowell SSC Guru Points: 323518 More actions · Answer 4

SQLWB.EXE = SQL Work Bench, otherwise knows as SQL Server Managment Studio; that's the executable you are using to look at and connect to SQL server, running the sqlserver.exe process.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Joy Smith San SSC-Insane Points: 24877 More actions · Answer 5

So

SSMS = sqlwb.exe

SQL server = sqlserver.exe

Am I right.?

Lowell SSC Guru Points: 323518 More actions · Answer 6

Joy Smith San (4/22/2010)
So
SSMS = sqlwb.exe
SQL server = sqlserver.exe
Am I right.?

yes that is exactly correct, Joy; you've got it now.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Joy Smith San SSC-Insane Points: 24877 More actions · Answer 7

Thank you. Kindly give some ideas on my first post as well.....

danfinuc SSC Enthusiast Points: 126 More actions · Answer 8

Might be useful to use perfmon to diagnose the problems. Though with 95% cpu usage, as others have stated...might be the cause of the problem. Look up useful techniques to measure memory/disk IO/ cpu useage. There is tons of documentation out there on setting this up.