Comments on: Index Defrag Script

By: John

John — Fri, 27 Nov 2009 22:13:10 +0000

I ran this script for a specific database. It completed successfully. Then I ran it in DETAILED mode (instead of LIMITED mode). What was strange was that many indexes still have 77% fragmentation or similar to what it was before. Why are the fragmentation numbers not decreasing?

By: Omega

Omega — Tue, 16 Dec 2008 19:18:26 +0000

нам что-то похожее препод вчера в универе рассказывал, на самом деле тема интересная

By: Michelle Ufford

Michelle Ufford — Tue, 16 Dec 2008 03:13:54 +0000

According to iGoogle, that means “I love all your words,” so thank you, Lena!

By: Lena

Lena — Mon, 15 Dec 2008 23:04:12 +0000

я люблю все ваши слова..

By: alex

alex — Fri, 12 Dec 2008 23:33:14 +0000

Add to my Bookmarks

By: Michelle Ufford

Michelle Ufford — Fri, 14 Nov 2008 22:29:10 +0000

Hi Chris! No, you’re not being thick. There are definitely components that will only work with Enterprise, such as the online and partitioning pieces. I don’t actually have SQL 2005 Standard installed, so I’ll have to install a copy and work on a Standard version of the defrag script this weekend. I’ll post the code when I’m done.

Regards,

Michelle

By: Chris K

Chris K — Fri, 14 Nov 2008 04:19:59 +0000

Hi Again. Say, is there any aspect of this that mandates Enterprise? I’ve tried running the script on my SQL Server 2005 Standard (sp2) database, but aside from creating the SP nothing appears to happen. No errors and I get “Command(s) completed successfully.”

Am I just being thick or am I running the wrong version?

By: Michelle Ufford

Michelle Ufford — Thu, 13 Nov 2008 15:07:27 +0000

Thank you, Roger! I have to agree with you, I’m eager for the day when MERGE-like functionality is also available for stored procedure creation. But I won’t hold my breath.

By: Roger

Roger — Thu, 13 Nov 2008 08:54:52 +0000

Michelle … may I compliment you on producing such a professional script.

This is just to state a forlorn wish that maybe someday soon MS will make this whole ridiculous Create/Alter problem go away (pipe dream I know!)

By: Michelle Ufford

Michelle Ufford — Wed, 12 Nov 2008 22:16:53 +0000

Hi Jason,

Great question! The biggest reason is that I try to avoid executing “DROP PROCEDURE” statements in production. Some of my stored procedures are called 500,000 to 600,000 times per hour. With those kinds of volumes, even a sub-second DROP / CREATE process will result in a few dozen errors. Given my desire to avoid that, it simplifies the deployment process to always prefix my stored procedures with that little piece of code.

Some of my colleagues also use the CREATE / ALTER approach to simplify deployments using PowerShell. This can be really useful when you’re deploying hundreds of stored procedures.

That said, this obviously isn’t one of those high volume procs, so the code is only there because it’s part of my standard stored procedure template. It really can easily be replaced with a DROP / CREATE statement, if you prefer.

Thanks for the question!

Regards,

Michelle