ApexSQL Defrag

Fix SQL index fragmentation

SQL Server index monitoring, analysis, maintenance and defragmentation

Analyze index fragmentation

Rebuild and reorganize fragmented indexes

Create and manage custom policies

Set schedules for defragmentation jobs

Set Email notifications

Monitor index fragmentation on multiple servers

Export all activities to CSV or XML

Create index fragmentation reports

Features

Index fragmentation analysis Search and analyze indexes by server,database, table, or index. Get detailed information on index type, size,fragmentation percentage, and fill factor with advanced grouping and filteringoptions.。                     Index defragmentation Reorganize or rebuild fragmentedindexes.                   Custom policies Use custom policies to automatedatabase index maintenance. Enable, run or disable a policy with a singleclick.                 Fragmentation threshold Set thresholds for reorganizing andrebuilding jobs.                   Job scheduling Set daily or weekly schedules forrebuild and reorganize jobs, or execute them in real time.                     Email notifications Set the Email notification forsuccessful or failed jobs.                   Monitoring Monitor all defragmentation jobs andpolicies from a central location.                     Activities export Export the activities to CSV or XML.                 Index fragmentation reports Create reports on index fragmentationand index memory usage for a database, table or a single index.

Save a bundle

ApexSQL Defrag is included in ApexSQL DBA

• 8 ApexSQL DBA tools
• Priority support
• 1 year free support and upgrades
• New products added for free
• Combined 70% savings

System requirements

Hardware requirements

Dual Core 2.0 GHz CPU

3 GB memory

200 MB disk space 

SQL Server

Microsoft SQL Server 2016, 2014, 2012, 2008, and 2005 

OS

Windows Vista/Server 2008 and above

Required 

Microsoft .NET Framework 4.5 

Note

Native support for the x64 architecture

Microsoft SQL Server Express edition is not recommended for the central repository, due to the database size limitation