LiteSpeed for SQL Server version 6.5 - defect or enhancement requests that have been addressed in release 6.5 of LiteSpeed for SQL Server.
Issues fixed in LiteSpeed 6.5.0, 6.5.1 and 6.5.2:
The following is a complete list of issues addressed and enhancements implemented in LiteSpeed 6.5.2 release.
The Restore Wizard may generate duplicate file names for a restore.
HTML reports are not sent to email recipients after upgrade.
The following is a complete list of issues addressed and enhancements implemented in LiteSpeed 6.5.1 release.
Automatic cluster installation may fail on a passive node.
Backup and Restore
LiteSpeed may fail to overwrite old Double Click Restore backups.
Fast Compression job may hang after the backup completed.
Backup to TSM may fail if the filespace name is longer than 99 characters.
Backing up with the "Optimize Object Level Recovery speed" option may cause the "Unable to access Temp directory () for OLR Map generation" error.
Smart Cleanup only removes one file in a multi-stripe backup.
Backups to UNC path are not deleted by the maintenance plan cleanup task or the "Remove files older than" option.
Object Level Recovery
Object Level Recovery may fail to recover a table if an empty system page is found.
Object Level Recovery may fail to recover a table with a persisted computed column.
Object Level Recovery should support the LIKE operator in queries.
Backup to TSM may fail with the error 'Unable to create backup sub directory "<name>". Error: "Access is denied"'.
Rebuild index task does not work on LiteSpeed local.
HTML reports are only created if the user also selects to create a text report.
Syntax example for xp_restore_database is incorrect.
The following is a complete list of issues addressed and enhancements implemented in LiteSpeed 6.5.0 release.
If the destination drive runs out of space to hold the backup file, LiteSpeed aborts but leaves an open SPID.
Server instances exported into SS2005 .regsrvr and SS2000 .csv files cannot be imported into the LiteSpeed UI Console.
Backup and Restore
LiteSpeed replaces double quotes with single quotes before sending the SQL to SQL Server.
Any scripts that may be using double quotes need to be reviewed and changed prior to upgrading.
Incorrect, will fail in LiteSpeed 6.5:
A backup cannot be restored if the encryption password is longer than 91 characters.
Changing the Init backup set option in LiteSpeed defaults does not affect the default shown in the backup wizard.
Ability to run LiteSpeed wizards, such as Remote Deploy and Instance Configuration using an account with no access to SQL Server.
Should display a warning if the server does not have .NET 2 SP1 installed prior to the installation of LiteSpeed.
Provide an option to ignore a server instance in the XML file to avoid installing LiteSpeed onto this instance.
Fill factor for the index is changed to 100 when using the Rebuild Index task.
Cannot open or convert a native SQL 2005 maintenance plan after LiteSpeed was upgraded to 6.1.
When saving a maintenance plan an error "Retrieving the COM class factory..." may occur.
Maintenance plans tasks other than backup should also have the option to ignore offline databases.
If a plan is disabled and then enabled later again it does not remember schedule settings and defaults to 1 hour interval.
The Copy Only Backup option is not scripted and not saved.
Object Level Recovery
Object Level Recovery may fail to read a backup with the "LSM File generation is not available" error.
The "Not null column was null" error may occur when restoring a table.
UI does not script out objects for recovery.
IDENTITY data type is not being transferred to the new table.
The @onFileGroup parameter only recovers tables to the PRIMARY filegroup.
Object Level Recovery should check databases for TDE and abort the request immediately if TDE is detected.
Object Level Recovery UI does not support Generate DDL Scripts and Recover of Schema against table names with Japanese characters.
Object Level Recovery may take several hours to complete recovering objects.
"Failed to read objects to recover" error may occur when reading a backup created with the previous LiteSpeed version.
"The DELETE statement conflicted with the REFERENCE constraint" error may occur when removing a subscriber from a log shipping plan.
If databases or SQL instances were renamed, the Update Native Backup statistics jobs can fail with the error "Cannot insert the value NULL into column 'DatabaseID'".
Central repository may update with the correct information from the local repository.
Maintenance plan history on LiteSpeed activity page is only updated after backup task completes.
Restoring a TSM backup using 'Restore from database' in UI errors out. 'Restore from Device TSM Backup' must be selected.
The TSM device retry time option is limited by 7 times.
The "Table <table_name> not found" error may occur when reading an offline log of a detached database.
The "Table 'sysfiles1' not found' error may occur when reading SQL Server 2008 offline database.
The "Page <page_details> is out of range" and "Page <page_details> not found" errors may occur when reading an offline database log.
Cannot sort jobs by the 'Enabled' and 'Last Result' columns on the LiteSpeed jobs page.
When standard license is installed, the UI allows to create a Fast Compression job if a database uses the simple recovery model.
Advanced Options selections are not retained after editing a log shipping plan.
Maintenance plan tasks are sometimes displayed incorrectly in the maintenance plan design window and cannot be scrolled to.
Better documentation regarding %z variable.
More details about file creation behavior with Fast Compression and Maintenance Plans.