Groups | Blog | Home
all groups > sql server clients > march 2006 >

sql server clients : Performance


Richard Douglass
3/31/2006 11:31:38 AM
I am having a problem with a customer. The app we are supporting was
developed using Client-Side queries that select * from views. Those views
are built using other views. (yes, layers of views) The performance isnt
all too bad, about 300 milliseconds per request. The optimizer loaded up
the underlying tables with tons of its own indexes and statistics. They
dont seem to help much when the queries are run isolated in QA.

I picked several tables and removed all optimizer hints and statistics,
leaving just the indexes from the app and the few we created for testing.
The performance was stable at about 250 milliseconds on average. No big
deal. Stayed this way for almost 2 weeks.

Last week the performance on the queries climbed to 1500 milliseconds for no
known reason. The CPU and DURATION are both approx 1500 all day long. No
code changes have been made, no settings changed, nothing.

Any ideas why I would see such a drop in performance?

Nils Loeber
4/17/2006 12:00:00 AM
Have you checked the index fragmentation on the utilized indexes?

Best,
Nils Loeber

"Richard Douglass" <RDouglass@arisinc.com> schrieb im Newsbeitrag
news:uAPu7mPVGHA.5724@TK2MSFTNGP10.phx.gbl...
[quoted text, click to view]

Andrew J. Kelly
4/17/2006 12:00:00 AM
It's quite possible you had a change that forced the plans to be recompiled.
Then the first time you called the query you passed a non-typical value that
is best treated with a scan instead of a seek. Try updating the statistics
and see if that helps.

--
Andrew J. Kelly SQL MVP


[quoted text, click to view]

AddThis Social Bookmark Button