SQL 2005 IndexDefrag solution

Question

Post reply

SQL 2005 IndexDefrag solution

Kobus-452994

Valued Member

Points: 68
More actions
May 7, 2008 at 8:01 pm

#190172

Comments posted to this topic are about the item SQL 2005 IndexDefrag solution

Viewing 5 posts - 1 through 4 (of 4 total)

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

Henrik Staun Poulsen SSCertifiable Points: 6582 More actions · Answer 1

Hi Kobus,

Did you see http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068

apart from the special scheduling (2:00 to 8:00) it looks as if it has more features than your procedure.

Best regards,

Henrik Staun Poulsen

Kobus-452994 Valued Member Points: 68 More actions · Answer 2

i have learned quite a bit since that post...it was 2 months ago...:):)

the most important thing that i leared was that you almost canot defrag a 2000 database on a 2000 SQL server, interestingly when we moved the database, the fragmentation was very high..i db reindexed it on 2005 with alter table and then did the magic bit...sp_updatestatistics...now i just manualy(via a shedule job) run sp_updatestatistics once a day...overkill but still...weird wonderfull world of windows...

Henrik Staun Poulsen SSCertifiable Points: 6582 More actions · Answer 3

Kobus,

Are you saying that running sp_updatestatistics manually "sorts things out"?

I must try that.

TIA

Henrik

Jeff Moden SSC Guru Points: 1004403 More actions · Answer 4

henrik staun poulsen (7/8/2008)
apart from the special scheduling (2:00 to 8:00) it looks as if it has more features than your procedure.

Which is why some people are driven to write their own. 😉

@Kobus,

That does bring up something important though. The article text says "2 to 4" but the code is actually setup for "2 to 8". If you have this code in production, that may cause you a problem sometime in the future.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)