Sudden occurance of process locks...what to do?

USING:  SQL SERVER 2000

Hi, we noticed the other day that we are getting a lot of process locks on the database coming mainly from our reporting application, cognos.  Performance is generally acceptable and not hampered.  However, the last few days users have been complaining about the slowness of their reports coming back in cognos.

Upon investigation, we are seeing that SQL Server has locks on majority of the requests coming through.  The locks are as follows:

PAGEIOLATCH_SH
LATCH_EX
CXPACKET

The wait resource varies to being blank, saying PARALLEL_PAGE_SUPPLIER followed by a number in brakets or just a wierd number that says something like 5:3:2130532 ....

In reading up on these locks I know they are lightweight locks and deal with network performance, parallelism, and i/o functions... but I'm not really sure what to do about it?

Is this something wrong with SQL that is causing these bottlenecks or is it the cognos application or is it our network?  Is there something in SQL I can do to remedy this or would the networking people need to get involved?

Thanks!
Roxanne25Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

8080_DiverCommented:
Can you add one or more covering indexes on the tables that COGNOS is using for the reports?
If you can do that, you may be able to decrease the database contention that is developing.
0
Roxanne25Author Commented:
No, I had made a post on here a few weeks ago about us having too many indexes! :)  We have some tables that have over 21 indexes on them.

I'm more interested in what is going on here and what exactly these locks are telling me.
0
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
<<Is this something wrong with SQL that is causing these bottlenecks or is it the cognos application or is it our network?  Is there something in SQL I can do to remedy this or would the networking people need to get involved?>>
At first stance, it looks like you have a blocking lock problem related to either poor caching or subsystem unability to respond to the engine request.  No need to involve your network people before you inquire on the blocking.

Please double check the following:

> Look at your procedure cache structure.  See the object count and see if you don't have inner memory pressure
> Look at your swapping RAM/IO.
> Look for your IO contention.
> Look if there not any deadlocks

HTH
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.