<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 Administration
»
Index Performance.
12 posts, Page 1 of 2
1
2
»»
Index Performance.
Rate Topic
Display Mode
Topic Options
Author
Message
abitguru
abitguru
Posted Tuesday, December 18, 2012 7:37 AM
Valued Member
Group: General Forum Members
Last Login: Monday, April 29, 2013 1:31 PM
Points: 71,
Visits: 264
Hi all,
I search a lot for this issue but I can't realize what happen.
The case is, randomly (no very often, but last two weeks happend) we experiment problems with performance in one particulary index (dont know if there are more)
We can see the performance issue becuase the query using the index is too slow (the table has 25 millon rows)
The problem solves when we re-create the index, but i dont certally know if this is a problem of index corruption.
For some reason we dont update statics (a month ago was last time)-
We use SQL 2008 sp3
1 - Could this be the reason of the index problem?
2 - Is there any way to check why the query is to slow?
Thanks for any help
greetings from argentina!!
Post #1397797
Sean Lange
Sean Lange
Posted Tuesday, December 18, 2012 7:52 AM
SSCrazy Eights
Group: General Forum Members
Last Login: Today @ 2:52 PM
Points: 8,605,
Visits: 8,246
gheinze (12/18/2012)
Hi all,
I search a lot for this issue but I can't realize what happen.
The case is, randomly (no very often, but last two weeks happend) we experiment problems with performance in one particulary index (dont know if there are more)
We can see the performance issue becuase the query using the index is too slow (the table has 25 millon rows)
The problem solves when we re-create the index, but i dont certally know if this is a problem of index corruption.
For some reason we dont update statics (a month ago was last time)-
We use SQL 2008 sp3
1 - Could this be the reason of the index problem?
2 - Is there any way to check why the query is to slow?
Thanks for any help
greetings from argentina!!
Try updating your statistics. That is almost certainly why your performance jumps all over the place.
_______________________________________________________________
Need help? Help us help you.
Read the article at
http://www.sqlservercentral.com/articles/Best+Practices/61537/
for best practices on asking questions.
Need to split a string? Try Jeff Moden's
splitter
.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Post #1397808
GilaMonster
GilaMonster
Posted Tuesday, December 18, 2012 7:53 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
Stale statistics. Almost certainly.
It's not corruption. Corruption doesn't cause performance problems. Corruption causes severity 24 error messages.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1397810
abitguru
abitguru
Posted Tuesday, December 18, 2012 8:01 AM
Valued Member
Group: General Forum Members
Last Login: Monday, April 29, 2013 1:31 PM
Points: 71,
Visits: 264
thanks !!!
in addition, we never see in logs an error about index damage,
we will try scheduling statics,
btw, how often is recomended statics update?
Post #1397819
GilaMonster
GilaMonster
Posted Tuesday, December 18, 2012 8:28 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
abitguru (12/18/2012)
in addition, we never see in logs an error about index damage,
As I said, it's not going to be corruption. (and one does not depend on the error log anyway to identify corruption in a database)
we will try scheduling statics,
btw, how often is recomended statics update?
You mean 'statistics updates'? Often enough that the queries using the statistics get accurate enough information. Yup, that's about all that can be said.
If you can afford to update stats daily, then do so.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1397841
peterdru401
peterdru401
Posted Wednesday, December 19, 2012 3:44 AM
Grasshopper
Group: General Forum Members
Last Login: Tuesday, April 16, 2013 8:34 AM
Points: 23,
Visits: 128
if you have too many indexes, the insert and update performance of your application suffers.
You have to find a balance between the indexing needs of the writes and reads that is based on how your application is used.
so you need to Reorganize indexing & update the stats
follow the below link to update the statistics
http://msdn.microsoft.com/en-us/library/ms187348.aspx
Post #1398274
abitguru
abitguru
Posted Wednesday, December 19, 2012 4:46 AM
Valued Member
Group: General Forum Members
Last Login: Monday, April 29, 2013 1:31 PM
Points: 71,
Visits: 264
thanks all for help me.!!
Yesterday we test UPDATE STATISTICS in our dev server (almost size of production). Now we are planing the best way to do in our production server.
Thanks again and greetings from argentina!
Post #1398309
TheSQLGuru
TheSQLGuru
Posted Wednesday, December 19, 2012 4:50 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 6:54 PM
Points: 3,578,
Visits: 5,120
I used statistics updates as frequently as every hour but for most systems that have some "slow/off time" over night then daily is plenty good enough. What usually ISN'T good enough is just letting auto update to the job. 20% mods can be a VERY long wait during which time significant amounts of queries get some bad plans.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1398312
abitguru
abitguru
Posted Wednesday, December 19, 2012 5:09 AM
Valued Member
Group: General Forum Members
Last Login: Monday, April 29, 2013 1:31 PM
Points: 71,
Visits: 264
thanks TheSqlGuru for your reply.
We dont use auto update. And is hard to find a "slow/off time" .. you know. We are thinking the best way to schedule to run in spare time.
In our server test takes 14 hours to complete the job. (less resources and almost the same database size)
Post #1398324
GilaMonster
GilaMonster
Posted Wednesday, December 19, 2012 5:51 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
abitguru (12/19/2012)
We dont use auto update. And is hard to find a "slow/off time" .. you know. We are thinking the best way to schedule to run in spare time.
If you have auto_update off then you
must
manually maintain your statistics (all of them). With it on, you can get away with just manually updating stats where the 20% threshold is too high.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1398339
« Prev Topic
|
Next Topic »
12 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
