LiteSpeed for SQL Server version 7.0 - defect or enhancement requests that have been addressed in release 7.0 of LiteSpeed for SQL Server.
Issues fixed in LiteSpeed 7.0:
The following is a complete list of issues addressed and enhancements implemented in LiteSpeed 7.0 release.
Create a subdirectory for each Database, similar to the function of backup task in Maintenance Plans.
Fast Compression fails on read-only databases
Ability to have fast compression create a sub directory for each Database backup.
Ensure that file names generated by Fast Compression do not exceed OS limits.
Fast compression is not calculating the changed extents correctly for a database with more than one file.
Ability to set a system wide temp directory for OLR via the registry. Handled via INI file
Licensing error be more "verbose"
OLR can not generate identity columns against numeric/decimal columns.
Unable to use a filter during OLR
Getting an incorrect syntax error while running OLR.
When a Litespeed Maintenance plan is stopped or canceled by the customer it immediately stops executing all backup task.
Ability to use EncryptionKey parameter with “open” password
Delete_LiteSpeedActivity be similar to the native SQL Server function where the archive/purge is based on the amount of rows, not their age.
When given a large amount of databases, slssqlmaint.exe will fail and give few clues as to why.
When running the following "exec LocalRepository..LiteSpeed_DeleteActivity @delLocal=1 (or @delCentral=1), ,@delStatus=1" the procedure run in chunks and then truncate the tlog file if needed.
Ability to attach directories to backups via an MP.
Manage Connections: once the connection is saved as sql authentication type, you cannot reverse it back to Windows.
The backup browser window does not sort directories alphabetical order.
Files and directory listings from a UNIX media server be in alphabetical order.
Unable to restore tlog when diff and tlog backup had the same "Begin" time
When deploying a template as a maintenance plan the option to create a subdirectory for each database is deselected for transaction log backups.
Ability to choose individual databases.
Allow changing/overriding Network Resilience settings via Advanced Options in Log Shipping.
Console not time zone aware
On the Backup Options screen the Acceptable Latency auto-adjust be greater than the current setting for Backup Interval.
Ability to select multiple transaction using the space or shift keys
When running xp_slsSmartCleanup in "Dryrun" mode include the day the backup file was created plus its expiration setting in the results.
The timeout on the TSQL commands\scripts that build the repositories indexes during an upgrade has been increased.
Installer Rolls back due to IS Custom action.
Double Click Restore examples added to help file.
Following information added in Help Files: Backup Templates may only be deployed as a job on SQL 2000 as maintenance plans are not available in this SQL version.
Logshipping guide updated to include that the SQL instances must first be registered in the LiteSpeed UI Console.
Limitation in Help Files. Ignore case parameter "i" in regular expressions does not work in Maintenance Plans.
Information about "threads" be removed from the help files for xp_slsrecast.
Ability to input SQL servers' IP address and port numbers in the UI during registration.
Litespeed console import the list of servers which have Litespeed installed via LiteSpeedCentral database.
Ability to capture output message after running xp_delete_tsmfile.
Ability for the UI to determine that a backup is either a TSM backup or TSM archive object and restore it.
Ability to use "@TSMPointInTime" or a subset of this parameter in the XP "xp_view_tsmcontents" to filter results.
Backups in progress' stat not showing activity
Ability to use the LS parameter %datetime%
Ability to set affinity for 64 to 128 processors.
When running a schedule multi-database backup ,which encrypts the backup file, on server with a Korean or Japanese windows OS the following error is seen "Failed to decode encryption key [SQLSTATE 42000] Error(60300)"
Fails with "The column prefix 't' does not match with a table name or alias name used in the query."
Confusing error messages generated by Litespeed's retry code.