Comments on: Index Defrag Script, v4.0

By: Index operation « Simon's SQL

Index operation « Simon's SQL — Thu, 12 Apr 2012 01:57:30 +0000

[...] http://sqlfool.com/2010/04/index-defrag-script-v4-0/ [...]

By: Spaceman

Spaceman — Thu, 14 Jul 2011 12:52:33 +0000

In response to my previous comment on the FILLFACTOR used i think it’s a misunderstanding because BOL is a bit contradictory…
“FILLFACTOR = fillfactor
Specifies a percentage that indicates how full the Database Engine should make the leaf level of each index page during index creation or alteration. fillfactor must be an integer value from 1 to 100. The default is 0.”

But later says…

“When an option is not explicitly specified, the current setting is applied. For example, if a FILLFACTOR setting is not specified in the REBUILD clause, the fill factor value stored in the system catalog will be used during the rebuild process.”

By: Spaceman

Spaceman — Thu, 14 Jul 2011 09:58:15 +0000

Had another thought on this great script. Would it be benenficial to limit the indexes in scope by table rowcount rather than by index pagecount?.
My thought here is that then i could have several jobs working overnight simultaneously, each one reindexing tables according to the tables rowcount. If i tried this using pagecount i suspect the jobs could end up rebuilding different indexes for the same table at the same time – which would probably cause some sort of contention problem.
Hope that makes sense… thanks.

By: Ninja RgR'us

Ninja RgR'us — Wed, 13 Jul 2011 13:34:45 +0000

Adjusted my script to allow for an exclusion list of databases (had a 2nd copy of prod db and doubled the maintenance time).

I’m sure I’m not the only one who needs this feature.

By: Spaceman

Spaceman — Tue, 12 Jul 2011 09:05:00 +0000

am i correct in thinking that the current script will use a default fillfactor of 0?… is so can it be changed to pick the indexes current fillfactor and use this in the alter index statement. Ta.

By: Ninja RgR'us

Ninja RgR'us — Mon, 04 Jul 2011 12:44:51 +0000

Just a quick note to say I love this script and recommended it over 30 times over on sqlservercentral.com

I’m currently working on a fill factor rework project and I’m using your log tables to pick the best candidates for changes. My “issue” is that you log everything EXCEPT the schema so it makes it a little hard to build my own commands from the history. I know it’s in the command column but since I’ll be redoing a couple 100 indexes I’d rather not have to work that hard to get it!

TIA.

By: Rob Johnson

Rob Johnson — Sat, 04 Jun 2011 14:22:32 +0000

Hi, have been testing this script, and have not really noticed a drop in fragmentation on a table with an index with a page count > 20 and fragmention percent > 30, but when I manually ran the ALTER INDEX command on this index with a FILLFACTOR = 1 statement included, the fragmentation level dropped to nearly 0. Have you ever considered adding logic to include a FILLFACTOR in your REBUILD INDEX logic?

By: Database Oil Changes – Part 2 | Art of the DBA

Database Oil Changes – Part 2 | Art of the DBA — Thu, 02 Jun 2011 13:19:45 +0000

[...] you don’t even have to write your own script! Go take a look at Michelle Ufford’s(b|t) Index Defrag script. It covers many of the possible scenarios for index rebuilding and, with all its parameters, [...]

By: MF4

MF4 — Mon, 30 May 2011 12:18:08 +0000

Hello,

Thank you for the script,

My problem is that the script run for 2:56:46 then failed.

Date 5/27/2011 10:00:00 PM
Log Job History (Index Defrag)

Step ID 1
Server *\*
Job Name Index Defrag
Step Name Run Script
Duration 02:56:46
Sql Severity 0
Sql Message ID 50000
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: *. …ssage 50000) Beginning validation… [SQLSTATE 01000] (Message 50000) Your selected parameters are… Defrag indexes with fragmentation greater than 1; Rebuild indexes with fragmentation greater than 30; You DO want the commands to be executed automatically; You want to defrag indexes in DESC order of the PAGE_COUNT value; You have not specified a time limit; minutes; ALL databases will be defragged; ALL tables will be defragged; We WILL be rescanning indexes; The scan will be performed in LIMITED mode; You want to limit defrags to indexes with more than 8 pages; Indexes will be defragged OFFLINE; Indexes will be sorted in TEMPDB; Defrag operations will utilize system defaults for processors; You DO want to print the ALTER INDEX commands; You DO want… The step failed.

Any direction you can point me to ?

Thank you,

By: RCP

RCP — Thu, 19 May 2011 17:03:11 +0000

THank you for developing this script. It has helped quite a bit in my work.

I am running into one issue that is problematic. I can run this script without issue when logged into SSMS but when I put the script into a SQL Server 2005 Maintenance Plan I always get the following error:

Possible failure reasons: Problems with the query, “ResultSet” property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1).

I have tried setting up various connections etc to no avail. Any help woudl be appreciated.

Thank you