Db Maint 4.0

Db Maint 3.0

Db Maint 2.0

What is the current version number?
The latest version of Db Maint is 4.0 (dbmaint.exe: 4.00.00, dbm.exe: 4.00.00), which is a major upgrade from 3.0.

Email notification fails (SQL Server 2000)
Db Maint version 3. Email notification might fails on SQL Server 2000. This has been corrected in dbm.exe version 3.00.69.

DBCC DBREINDEX not performed on SQL Server 2000 (SQL Server 2000)
Db Maint version 3. DBCC DBREDINDEX is not performed when SQL Server version is 8.0 under some circumstances. This has been corrected in dbm.exe version 3.00.68.

Select into/bulkcopy and large transaction log file
Db Maint version 3. If select into/bulkcopy is set and truncate log on checkpoint is not set (bulk-logged recovery mode), then dbm performs a database backup at log occasions (instead of a log backup). This was by design to minimize loss of data (if non-logged operation has occured a log backup would fail in versions prior to SQL Server 8.0). This can lead to databases for which no log backup is performed, hence the transaction log files can grow very large. This has now changed, dbm tries to perform a log backup and generates an error message if SQL Server returns an error message. To reduce size of transaction log files, turn on the autoshrink database option for a period of time (don't forget to switch it back off). Fixed in dbm.exe 3.00.67.

Error when open log details in Main pane
Db Maint version 3. When you double-click on a task execution an error message is returned if there are more than 32000 task execution rows. Fixed in dbmaint.exe 3.00.66.

Cannot start SQL Server Agent on Named Instance
Db Maint version 3. Fail to start SQL Server Agent on a Named Instance. Fixed in dbmaint.exe 3.00.64.

Error when checking for free disk space
Db Maint version 2. Error when checking for free disk space. This happens on partitions with more than than 32GB unused space. Fixed in dbm.exe 2.02.03.

Windows 2000 support
Db Maint version 3.0 supports Windows 2000. Db Maint 2.x will not be fully tested on Windows 2000. There are no known problems as of version 2.02.02.

Unable to logon to SQL Server.
Db Maint version 2. This happens if Db Maint is unable to establish a trusted connection to the SQL Server. This has been fixed in 2.0.70.

The server properties dialog is too big for standard VGA resolution
Db Maint version 2. Workaround: Run the Db Maint program from a machine with higher resolution (a client, possibly). This has been fixed in 2.0.70.

Calling a stored procedure with a long name from a job.
Db Maint version 2. Db Maint limits the length of the string (name of stored procedure plus its parameters) to 30 characters. This limitation was relaxed to 255 characters in 2.0.80.

Calling a stored procedure where the string includes single-quotes.
Db Maint version 2. This was not supported in builds prior to 2.0.80.

Jobs that were executed for the built in All group does not perform INIT for the backup device
Db Maint version 2. This has been known to happen in rare occasions in previous versions of Db Maint. The problem was fixed in 2.0.80.

Backup not performed when backing up database group with backup generation
Db Maint version 2. This has been known to happen in rare occasions in 2.0 and previous versions of Db Maint, depending on the the number of databases included in the database group. This problem was fixed in 2.0.1 (2.01.11).

Postrun not executed when using Quick Setup
Db Maint version 2. This problem was fixed in 2.0.1 (2.01.11).

Tasks executed with Db Maint 2.01 terminate with IN PROGRESS status
Db Maint version 2. This happens in the following situations: You have backup generations, are running 2.01.11 of dbm.exe and are using a case-sensitive SQL Server. The problem is resolved in 2.01.12.

Error when logging to master server
Db Maint version 2. This occurs if SQL statement to log includes one or more aphostrophes. The bug was fixed in dbm.exe build 2.01.13.

Messages in Db Maint log which states that the execution of ISQL failed
Db Maint version 2. This can happen if SQLServerAgent's current path has a long directory name in it. The bug was fixed in dbm.exe build 2.01.13.

SQL Server error 416
Db Maint version 2. Error 416 reported by SQL Server. Task terminated. This is due to a bug in SQL Server 6.5. Make sure that you have at least SQL Server service pack 2 or later installed if you are running 6.5.

Incorrect x-axis headers in performance viewer
Db Maint version 2. The x-axis headers in the performance diagram dialog is not correctly numbered. However, the values displayed are correct. The bug was fixed in dbmaint.exe build 2.01.12.

Error message referring to dbmsysusages table on upgraded SQL Server 7.0
Db Maint version 2. An error message is written to the Db Maint log referring to the dbmsysusages table on upgraded SQL Server 7.0. This only happens if the SQL Server was upgraded from 6.5. Solution: delete the dbmsysusages table. This is easiet done from Enterprise Manager. You can also issue the following statement from Query Analyzer "DROP TABLE msdb.dbo.dbmsysusages". The dbmsysusages table has no function on version 7.0 and should have been removed automatically by Db Maint. The bug was fixed in dbm.exe build 2.02.0001.