SQL Defrag Manager provides the following new features
...
3.1 New features
New SQL Server 2012 support
SQL Defrag Manager 3.1 is SQL Server 2012 RTM compatible. This version of SQL Defrag Manager is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. Idera provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as, or better than, expected.
3.1 Fixed issues
There are no fixed customer issues in this release.
Need more help? Search the Idera Customer Support Portal
:
3.8 New features
- Support for SQL 2022
SQL Defrag Manager now supports SQL Server 2022.
3.7 New features
- Adding a 'Frag %' column to the ToDo Table
SQL Defrag now offers users the ability to select an index rebuild and have the fragmentation percentage displayed.
- Ability to Send Schedule Reports via Email
SQL Defrag now has the ability to automatically send scheduled reports email, to contacts in its defined list.
- Upgrade SQL Defrag Manager .NET Dependency
SQL Defrag Manager .NET dependency was upgraded to version 4.8 in order to have better performance, efficiency, and product security.
Expand |
---|
|
3.6 New features- Recurring Automated Policies
SQL Defrag now allows policies to run more than once a day
- Setting Up Automated Policies with Different Analysis Types
SQL Defrag now offers users the ability to run policies using different Analysis Types - New "Instant Defrag" tab
Rebuild or reorganize all the displayed fragmented hotspots at once with a click of a button
|
Expand |
---|
|
3.5.1 New features- Support for SQL 2019
SQL Defrag Manager now supports SQL Server 2019 and update .NET for Management Server and Data Repository
- Cloud for Azure and AW EC2
Cloud environment for SQL Defrag to test on Azure and AW EC2. For more information visit Cloud for Azure and AW EC2
- Support for Windows 2019
SQL Defrag Manager now supports Windows 2019 and updated .NET for console - Support for SQL Server 2019 Database
SQL Defrag Manager now supports SQL Server 2019 Database Platform - Support for databases in Azure
Support for databases hosted in Azure instances
|
Expand |
---|
|
3.5 New features- Support for SQL 2017
SQL Defrag Manager now supports SQL Server 2017.
- Auto-discovery
A new option has been added to policies allowing users to configure auto-discovery of server objects when the policy runs
- Show a table's schema
Hovering over a table in the Targets section of the Policy wizard displays a table's schema as a tool tip.
- Recent Activity Configuration
Configure the maximum number of displayed items on the Recent Activity pane. You can find more information here.
|
Expand |
---|
|
3.4 New features- This release does not add extra functionality
|
Expand |
---|
|
3.3 New features- Import policies
Allows you to import policies from XML files. Click here to learn more. - Export policies
Allows you to export policies to XML files. Click here to learn more. - Navigation tree filtering option
Allows you to filter the items displayed in the SQL Defrag Manager Explorer by specific name or by keywords (using wildcards). Click here to learn more. - "Rediscover Objects" action for databases and tables
Allows you to quickly Rediscover Objects within a specific database or table. Click here to learn more.
|
Expand |
---|
|
- Supports SQL Server 2014
SQL Defrag Manager supports the use of SQL Server 2014. - Includes a new CLI option that initiates a defragmentation from the command line
SQL defrag manager 3.2 includes a new command line option that initiates a defragmentation. Use the following CLI option:
sqldefragc [[[–rebuild [online]] | –reorg] –instance <instance name> –database <database name> | –policy <policy name>] You have two options when using this code. You can: - Define the defragmentation as follows: specify "rebuild" or "reorg" where "online" is optional for "rebuild"; specify the "instance name"; and specify the "database name". - Define the defragmentation based on an existing policy by specifying the "policy name".
|
...