Db Maint What's new in 4.0

Home

Products
Order
Partners

What's new in 4.0
Key features
Feature list
Books online
Screenshots

Press releases
Press clippings
References

Support
Knowledgebase
Download
Free utilities

Contact us

Db Maint version 4.0 is a major new release. The scheduling has been reworked in order to increase flexibility and to make Db Maint easier to use and understand. Also, instead of doing append to backup devices, Db Maint now creates a new backup device each time a backup is performed. This is more in line with the way that most database administrators perfer to work and also allows for features such as test restore, log shipping, compression and archiving of backups.
Db Maint 4.0 contains many enhancements and new features. The most important ones can be found below:

Scheduling is easier to understand and use, yet more flexible
A job specifies which operations (backup, reorganization etc) to be performed against a database or a set of databases (a database group). A task includes a number of jobs, and you decide when each operation is to be performed. Schedule tab Example:
  • Database backup at 01
  • Log backup at 03, 05, 07, 09 - every 15 minutes - 17, 19, 21, 23
  • Reorganization every week at 02
  • Consistency check at 03
  • Collect performance counters every 10 minutes

Support for differential backup
Backup tab

Copy backup files
Immediately after a backup is performed, you can specify that the backup file is copied to a desired location. For example, you might do log backup each hour and copy the backup files to tape once a day. You would risk one day worth of data if the machine crashes. By immediately copying the backup file to another machine, you drastically reduce the risk of losing data. General tab

Archiving of backup files
You can specify that Db Maint will take an archive copy of a backup file every month, quarter, half year or year. Archives copies will not be deleted automatically as original and copy backup files are (you can specify number of days to keep original and copy backup files).

Compression or other post-processing of backup files
Backup files tend to compress very well. You can specify a compression command to be executed after the backup is performed. Whether to compress can be specified independently for original, copy and archive backup files. Backup tab General tab

Test-restore and log shipping
Only way to be certain that you can restore a backup is by ... restoring it. It is very easy to specify that a test-restore is to be performed after each backup (you first specify location for database files and prefix for test-restore database names). You can also choose to continuously restore the backups onto another standby server (log shipping), as a fault tolerance mechanism. It is very easy to set up and the backups shipped to the other machines are fully integrated with the ordinary backup schedule. Backup tab Backup tab

Email notification through SMTP
Naturally, Db Maint still supports email notification through MAPI. But the MAPI support can be a hassle to install, get working and maintain. Db Maint can now send email notifications using SMTP. Email settings tab Log tab

User defined menu-items
You can add your own menu-items which are available when you right-click a server, database, table or index. You specify which TSQL command(s) are to be executed when you select each menu-item. These are context-sensitive, meaning that you specify a placeholder for the server-, database-, table- and/or indexname which will be substituted at execution. You can also specify up to 6 other parameters. These menu-items are stored in a table on the server, hence they are available for all clients. Db Maint comes preconfigured with over 50 such menu-items. User defined commands

Other new features
Below is a short list of some other new features and enhancements. You might want to go through the screenshots which will give you a feel for version 4.0. Or download the time-limited but fully functional trial version.
  • Map orphaned users
  • View fragmentation information
  • View space usage information per table/index in a database
  • Task-level pre- and postexecution TSQL batches
  • Reorganization using DBCC INDEXDEFRAG
  • Checkdb using PHYSICAL_ONLY
  • Finer granularity for the HTML log
What's new in 3.0
What's new in 2.0