Idera strives to ensure our products provide quality solutions for your SQL Server needs. The following known issues are described in this section. If you need further assistance with any issue, please contact Support (www.idera.com/support).
There are no new installation and configuration considerations in this release.
There are no new known issues in this release.
Idera is phasing out all Itanium support in SQL Defrag Manager 3.0 and all subsequent versions. SQL Defrag Manager 3.0 does not support the Itanium processor architecture and limited technical support is available through November 2012. For more information, see the product requirements.
If you select a SQL Server 2000 database and select the Thorough analysis type, SQL Defrag Manager performs a Fast analysis for that database.
Small indexes may not meet your fragmentation threshold levels and can cause SQL Defrag Manager to display errors on the Recent Activity tab. When SQL Defrag Manager analyzes and defragments a database, it displays an error message on the Recent Activity tab for each index that it cannot sufficiently defragment. Small indexes often have fragmentation levels that cannot be reduced. By default, SQL Defrag Manager excludes small indexes from the Fragmentation Explorer tab. You can also modify your automation policies to ignore the fragmentation level of small indexes.
If an analysis process fails, SQL Defrag Manager does not update the fragmentation information displayed on the Fragmentation Explorer tab. SQL Defrag Manager displays that fragmentation information from the last successful analysis.
When you export information from a tab, such as the Scheduled Activity tab, to an HTML file, the column headings may be truncated for narrow columns. To avoid this issue, export the information to an XML file.
When you register instances on a server, SQL Defrag Manager may not list all instances on that server. You can add missing instances by name to register those instances.
SQL Defrag Manager supports the following 64-bit software versions:
A policy configured to use the CPU Load Percentage (Total Server) resource check does not work correctly if OLE is disabled on the server.
When a user with SQL Server 2000 performs a rebuild of a clustered index, SQL Server also rebuilds all non-clustered indexes. This issue occurs during all clustered index rebuilds, including when the user accepts a change to the fill factor settings as that feature requires a rebuild of the clustered index.
Users with partitioned indexes and who upgrade from a previous version must use the Rediscover server objects feature for SQL Defrag Manager to recognize partitions. To rediscover these objects, right-click the appropriate server name while in Fragmentation Explorer, and then select Rediscover server objects.
Need more help? Search the Idera Customer Support Portal
| Idera Website | Products | Purchase | Support | Community | About Us | Resources | Legal |
|---|