June 03, 2009 06:03 PM

Review: SQL defrag manager 2.5

Rating: (0)
SQL Server Magazine
InstantDoc ID #102030

Executive Summary:

SQL defrag manager 2.5 lets you quickly analyze indexes and defragment them. SQL defrag manager 2.5 lets you automate index defragmentation by creating policies, which can be scheduled, in which you can specify thresholds for fragmentation levels and index scan densities. Although SQL defrag manager 2.5 has great features and an easy-to-use GUI, its high price prevented it from getting 5 out of 5 stars.


Properly managing index density and fragmentation levels can be very time-consuming. Having spent my fair share of time in the trenches, I was happy to take a look at Idera's SQL defrag manager 2.5 to see what it had to offer. Overall, I was very impressed with what I found.

SQL defrag manager 2.5 is a GUI that wraps existing T-SQL functionality for index analysis, defragmentation, and optimization. It lets you quickly analyze and manually defragment indexes with just a few clicks of the mouse. Moreover, SQL defrag manager makes it pretty easy to do at-a-glance index management by utilizing a dashboard approach that can be easily configured to highlight indexes, tables, or databases with problems.

When analyzing SQL defrag manager 2.5 and putting it through the paces, I was impressed by how smoothly the installation went, and how easy it was to get everything set up. There’s no need to install any agents on your managed servers. Instead, the installation process creates a new database that acts as a repository for policies, as well as scheduling and historical data that can be used with the UI or admin console (which can be installed on any client machine).

The admin console has a Microsoft Office ribbon look and feel that makes navigating to different options and features a breeze. During my review, I noted that features are easy to discover, and everything about this tool is intuitive and easy to understand. More importantly, SQL defrag manager makes manual analysis and correction of index fragmentation a snap using the Fragmentation Explorer, which displays object hierarchies, index metrics, and fragmentation details.

Where SQL defrag manager really shines, however, is by enabling automated index defragmentation. By using the admin console in conjunction with the specialized Defragmentation Service and the repository (or custom database) created during installation, you can easily create policies (or jobs) that can be scheduled as needed. Policies are easy and intuitive to configure, and you can specify thresholds for fragmentation levels and scan densities (as well as filters for what kinds of conditions to ignore) that indicate when you need to take action. Policies respond to fragmented indexes by rebuilding or reorganizing them.

Flexibility and control are rampant throughout the policy creation process. For example, policies can target entire servers, all the indexes of a given table, or selected indexes on one server and a handful of indexes on another. You just have to select which objects you want to be included from a tree view of registered servers and specify other criteria as needed via the appropriate tabs used for policy definitions, as shown in Figure 1.

One of my favorite features enables policies to take no action; instead, problematic indexes are dropped into a to-do list where they can be manually and individually analyzed and dealt with. Another place in which SQL defrag manager shows considerable maturity and real-world clout is when it comes to defining Resource Checks that can be evaluated prior to each policy being executed, as shown in Figure 1. With this feature, you can craft moderately aggressive defragmentation policies but still ensure that if an extraction, transformation, and loading (ETL) job runs a bit late, policy execution won't bring the server to its knees by blindly starting when scheduled.

Sadly, as cool and powerful as SQL defrag manager’s policies are, there's no way to fire them off manually. So, if you've got a policy defined for a few problematic tables that you need to run on a semi-regular basis, you either have to manually defrag those tables or temporarily tweak the policy’s schedule. This is a big limitation in my mind because it prevents you from using of SQL defrag manager's more powerful capabilities in ad-hoc fashion. Another negative factor that I encountered was that DROPed tables kept showing up in the UI, and trying to force re-scans of the dropped tables resulted in errors.

Even with those quirks, I would have given SQL defrag manager a nearly 5 out of 5 rating if it weren't for its pricing. As amazing as this tool is, at $1,195 per managed server, it's overpriced. Although Idera offers discounts for volume licenses, it doesn't make that blatantly obvious on its website. Still, this solution has some great features and can help cut costs in terms of administrative effort, so it's definitely worth an evaluation.

SQL defrag manager 2.5
Pros: Well designed UI makes manual analysis and defragmentation a snap; automated analysis (via policies) is easy to configure and very versatile and flexible in terms of scope and capability; can save lots of time; excellent for both granular and exhaustive multi-server management
Cons: Policies can't be manually executed (only scheduled); doesn't react well to DROPed or renamed tables and indexes; ideal for environments with lots of SQL Server instances, but Idera isn't very clear about bulk licensing costs on its website
Rating: 4 out of 5
Price: $1,195 per managed server
Recommendation: SQL defrag manager 2.5 does a fantastic job of wrapping SQL Server's native index defragmentation tools with a very intuitive and useful UI, and its automation policies are much easier to work with than custom scripts and jobs.
Contact: Idera • 877-464-3372 • www.idera.com

Add a Comment

Mike,

Yesterday I finally reached someone within the Idrea support group who knows their way around this application. We had a very informative live meeting session and have logged a number of bugs to be corrected and also some feature requests. The ability to execute and stop policies in an ad-hoc fashion was one of the feature requests. Another was to fix the schedule operation so that it more closely resembled the sql server enterprise manager or management studio job setup and scheduling functions (with the ability to execute a daily job more than 1 time per day, per discussion with Idera yesterday the current scheduling code prohibits re-execution of any daily schedule if it has already run that day). Seeing as the vast majority of users of this application will have a sql server dba background I would have thought that the development gurus behind this application would have figured this one out by themselves.

Another bug exists in the scanning of the tables and indexes. If you configure a run-once policy to scan and re-org your tables in a database and then re-schedule that policy to scan again, the second scan does not scan all of the tables, this issue is still open and I am waiting on feedback from idera on this one.

The idea behind this application is very good but as I mentioned in my prior comment, the execution and particularly the QA process leaves much to be desired. I have been the personal QA department for this application for the past 5 weeks. I am hoping that in the next release most or all of these bugs will be fixed. If these bugs are fixed and some of the new features are implemented THEN I could justify the $1200 per instance license cost. At this point we feel slightly cheated that we are out of pocket for 3 instances using this buggy version of the application but we will make do and work around these issues as best possible for now.

Michael8/13/2009 1:22:54 PM


@mconnolly06 - I covered the negative aspects of scheduling and the fact that the application doesn't seem to be able to pick up schema changes (specifically, DROPPED tables) in my review - and even pointed out that I think they represent pretty significant limitations.

I wasn't aware of the issues with scanning more than a single instance at a time - so that's my bad.

--Mike

Michael8/12/2009 12:20:00 PM


Dear Editor,

I have been evaluating SQL defrag manager for the last 4 weeks at my company and I have to say that the review that you gave this product was far too generous. The concept behind the application is great but the execution by Idera leaves much to be desired.

Over the past 4 weeks I have logged 12 bugs with Idera, (Including 2 today 8/11/09). I have been in contact via email with our account manager as well as the VP of the company and multiple different support engineers and associates.

We have the latest version of the application, fully licensed to manage our instances. I cannot explain in words how buggy this application is but I will list just a couple of the issues that I have reported.

It is not possible to scan more than 1 instance at the same time. So if you are planning on managing your index fragmentation on more than 1 instance during the same time window this is not possible. This bug alone makes the application unusable in a normal production environment. Who wants to schedule different maintenance windows just because the application being used to manage the indexes cannot perform more than 1 scan at the same time. This is a massive defect in my opinion.

If you are using this in a test environment (or running eval) you cannot change the scheduled time on a one-time policy to have it run again the following day. You will need to re-create the policy from scratch. The scheduler piece of the application is froth with bugs.

After you register a server instance to me monitored the application connects to the instance and retrieves the list of tables and indexes. All scans from that point assume that the table and index list will never change. You can manually right click on an instance and choose "re-discover server objects" but this process will never happen automatically. If you do add a new table your scheduled policies will error and stop.

Many many more bugs but I'm out of chars to type. This application needs work!

Michael8/11/2009 12:13:01 PM


You must log on before posting a comment.

Are you a new visitor? Register Here

Field data type change - query timeout

Hi,       I need to change a data type of a field in SQL Server 2005. The fiels most be changed from varchar(13) to varchar (20), but because of th...222-96220

GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS