LiteSpeed for SQL Server version 5.2.0 - defect or enhancement requests that have been addressed in release 5.2.0 of LiteSpeed for SQL Server.
Installation wizard displays a confusing summary on the completion page when option to not install Activity Logging is chosen.
Installer should perform the same way on uninstall as it does when installing to a multi instance cluster.
Cluster installs require that the LiteSpeed .msi file must be run on all active nodes.
Instance configuration wizard should recognize cluster instances that already have LiteSpeed installed, and set these instances to Ignore in the SQL Instances screen.
Backup and Restore
IntelliRestore option is no longer available when selecting TSM objects using the Restore Wizard.
Focus is on folder rather than file when selecting/changing data file locations in the Restore Wizard.
Restore fails with the "Restore cannot process database <databasename> because it is in use by this session. It is recommended that the master database be used when performing this operation" error.
Restore fails if sector size of restore device does not match the sector size of the device used for backup.
Attached files FileSet module code has bug which is triggered by bad parameters passed in and fails the reads.
LiteSpeed backups fails on Japanese OS.
Encryption is disabled after an upgrade from 5.0.2 (JAPANESE).
LiteSpeed on Japanese environment fails to pick up the LiteSpeed version in the Backup Wizard, thereby SmartDiff is not available.
The @verify parameter fails xp_backup_database on mirror backup file.
The stored procedure xp_backup_database does not work with Unicode characters in the database name.
Arithmetic Overflow error when attempting to process database more than 2 TB in the Backup Analyzer.
LiteSpeed should have the equivalent command to BACKUP LOG dbname TO DISK = 'nul'.
Restore fails without SQL error return code - @@err does not work.
Column datatype used for storing LSNs may cause log shipping to fail.
Locks on LogShippingHistory table should be eliminated.
Log shipping jobs intermittently fail on the restore because of skipped transactions.
The "Value cannot be null" error occurs when saving SQL 2005/2008 plan with a backup task configured to use a remote connection to SQL 2000.
Upgrade native tasks to match functionality of backup task in regard to offline databases (if the backup task is ignoring offline databases, the other native tasks should also ignore offline databases, regardless of SQL version).
When entering a value in the Max transfer size field, it is keeping whatever is typed in on a 64K boundary.
License check should be performed prior to creating and saving a maintenance plan that includes a SmaftDiff task.
Upgraded Maintenance plans fail on verify step if backup is encrypted.
Read-only databases are not backed up if the Ignore Offline Databases option is selected.
Read-only databases cannot be included in the backup task for maintenance plans.
When creating a maintenance plan to backup databases using TSM there is no option to create a new file space.
The "local connection cannot be found" error may be encountered on German SQL servers.
Advanced properties of the Select database window are not available in the Check Database Integrity and Rebuild Index tasks.
SupportComputedColumn parameter should be supported in xp_slssqlmaint.
xp_slssqlmaint fails to work properly with multibyte characters.
Object Level Recovery
OLR fails with error "Table <tablename> not found in backup file" if non-English characters or symbols are in the object name being restored.
When recovering an object with the Generate DDL Script option a server connection error may occur.
Error "Index was outside the bounds of the array" when importing SQL Server Registration values.
Importing SSMS .regsrvr export file using LiteSpeed Import 'From File (.csv)' option return the error: 'Column 'Password' does not belong to the table'.
Support for empty "@" parameter for TSQL statements.
The specified @server_name ('<servername>') does not exist.
"ad hoc update to system catalogs is not supported" error occurred when attempting to expand instance in UI