LiteSpeed® for SQL Server
Version 5.2.0
Release Notes
October 2009
LiteSpeed for SQL Server is a revolutionary, patented development in database backup technology, encompassing the latest encryption and compression algorithms to deliver a complete solution for your archiving needs. LiteSpeed maximizes disk space and process efficiency while greatly reducing the overhead costs associated with maintaining a state-of-the-art database facility.
The size of the backup file is typically only a fraction of the size of the original database. This maximizes storage efficiency and saves significant disk space. Encryption ensures that data cannot fall into the wrong hands as it is transported to an off-site backup facility.
Downtime and database failures are a reality. Components fail, databases become corrupted, and administrators make mistakes. But by using LiteSpeed, you can reduce restore time and minimize downtime. Mission critical databases can be brought back online quickly and reliably using LiteSpeed’s revolutionary technology.
For more information about LiteSpeed and interaction with other users, visit the LiteSpeed Community web site at http://sqlserver.quest.com.
Key Benefits:
SmartCleanup will maintain on disk a full backup set and intelligently remove backups that are no longer needed to restore the database. SmartCleanup is integrated with SmartDiff in the UI and available for use outside of SmartDiff with the following new procedure and command-line executable:
New, default "Enable backup escalation" option automatically issues a full backup if a problem is detected with the existing backup set.
The following is a list of issues addressed and enhancements implemented in the LiteSpeed 5.2.0 release:
|
Feature |
Resolved Issue |
Defect ID |
| Installation | Cluster installs require that the LiteSpeed .msi file must be run on all active nodes. | ST#62155 |
| Instance configuration wizard should recognize cluster instances that already have LiteSpeed installed, and set these instances to Ignore in the SQL Instances screen. | ST#66166 | |
| Backup and Restore | IntelliRestore option is no longer available when selecting TSM objects using the Restore Wizard. | ST#53610 |
| 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. | ST#66083 | |
| Restore fails if sector size of restore device does not match the sector size of the device used for backup. | ST#66555 | |
| Encryption is disabled after an upgrade from 5.0.2 (JAPANESE). | ST#67225 | |
| Log Shipping | Column datatype used for storing LSNs may cause log shipping to fail. | ST#66496 |
|
Maintenance Plans |
Upgraded Maintenance plans fail on verify step if backup is encrypted. | ST#66998 |
| When creating a maintenance plan to backup databases using TSM there is no option to create a new file space. | ST#56990 | |
| The "local connection cannot be found" error may be encountered on German SQL servers. | ST#66592 | |
| Object Level Recovery | When recovering an object with the Generate DDL Script option a server connection error may occur. | ST#65883 |
| Server Import | Error "Index was outside the bounds of the array" when importing SQL Server Registration values. | ST#63020 |
| Engine |
The specified @server_name (' |
ST#60243 |
| TSQL | Support for empty "@" parameter for TSQL statements. | ST#61186 |
| UI | "ad hoc update to system catalogs is not supported" error occurred when attempting to expand instance in UI. | ST#55998 |
| Other Issues | Information on other resolved issued may be found in the Quest SupportLink Knowledgebase under SOL58072. These resolved issues include the following change requests: ST#67421, ST#67391, ST#67014, ST#67012, ST#66951, ST#66594, ST#66548, ST#66175, ST#65965, ST#65954, ST#65886, ST#65403, ST#65260, ST#65217, ST#65174, ST#65145, ST#64856, ST#64370, ST#62996, ST#61565, ST#60884, ST#59627, ST#53549, ST#38767 | N/A |
The following is a list of issues addressed and enhancements implemented in the LiteSpeed 5.1.1 release:
|
Feature |
Resolved Issue |
Defect ID |
| Backup and Restore | Backup performance in 5.1.0 may be slower after upgrading from a previous version. | ST#65354 |
| When restoring from tape the user may encounter the following error: "The file on device '\\.Tape0' is not a valid Microsoft Tape Format backup set." | ST#64849 | |
| Point-in-time restores sometimes fail in non-English locales. | ST#61804 | |
| A Restore job may fail with the following error: "RESTORE requires MAXTRANSFERSIZE=xxxxxx but yyyyyy was specified." | ST#63104 | |
| When running SmartDiff, the LSN (Log Sequence Number) verification may fail when creating differential backups. | ST#65502 | |
| When using the Restore wizard, a user may not choose a single file group against a full database backup that has multiple file groups. | ST#57386 | |
| When restoring file groups, the Restore Wizard may generate an incorrect script. | ST#60420 | |
| When restoring a "double-click" restore package, the Restore Wizard may generate an incorrect script. | ST#60338 | |
|
Log Shipping |
Restore jobs may intermittently fail when shipping large files over slow network. | ST#65044 |
|
Maintenance Plans |
Users may encounter the following error, “Could not locate entry in sysdatabases for database,” when a database is deleted subsequent to plan creation. | ST#59987 |
| When running maintenance plans, users may encounter the following error: "Incorrect syntax near the keyword COMMIT." | ST#65182 | |
| The backup file name does not contain the seconds data in the timestamp. | ST#60359 | |
|
Object Level Recovery |
Users may encounter an error when recovering a table with persisted computed columns. | ST#63060 |
| OLR now supports reading "double-click" generated restore files. | ST#62590
ST#53781 |
|
|
Other Issues |
Information on other resolved issued may be found in the Quest SupportLink Knowledgebase under SOL56050. These resolved issues include the following change requests: ST#65894, ST#65528, ST#65502, ST#65486, ST#65354, ST#65346, ST#65344, ST#65256, ST#65182, ST#65181, ST#65044, ST#64849, ST#63775, ST#63326, ST#63104, ST#63060, ST#62735, ST#62590, ST#62490, ST#61804, ST#61665, ST#61479, ST#60420, ST#60359, ST#60338, ST#59987, ST#59660, ST#57882, ST#57386, ST#53781, ST#53205, ST#51960, ST#48383 | N/A |
The following is a list of issues addressed and enhancements implemented in this release:
|
Feature |
Resolved Issue |
Defect ID |
| Installation/Upgrade | An inaccurate error message was returned when a .msi file that did not exist was specified from the Remote Deploy Configuration Wizard. |
ST#57801 |
| Object Level Recovery | Large table/database OLR restores consistently failed immediately after being started. | ST#52892 |
| OLR was unable to display the results for queries containing MONEY datatypes in the WHERE clause. | ST#60851 | |
| OLR was unable to handle queries for REAL, FLOAT, DECIMAL and negative values in the WHERE clause. | ST#58978 | |
| Maintenance Plans | During backups the execute T-SQL task was not executed when there were other tasks in the subplan. | ST#55934 |
| The Notify Operator task failed when the notification message was empty. | ST#56515 | |
| A legacy Maintenance Plan failed when 'email report to operator' was selected in the Reporting task. | ST#59984 | |
| The Maintenance Plan, created on the original instance/node, failed when the cluster was failed over to other node. | ST#56365 | |
| Backup and Restore | Using compression level = 1 on an Itanium box caused slow backup performance. | ST#58438 |
| The Restore Wizard Transaction Log Script contained an unnecessary MOVE parameter. | ST#60319 | |
| Restoration of a backup using a converted Maintenance Plan failed with an error message about the MAXTRANSFERSIZE. | ST#61414 | |
|
Log Shipping |
When two or more publishing databases share a similar name and were backing up to the same LogShipping share, a database backup by one would overwrite or delete the other backup files. | ST#54638 |
|
Log Reader |
The Transaction Log could not be read from a 64-bit client. | ST#57973 |
|
Job Manager |
When copying a backup job from one server to another, the copy succeeds but the job step is incorrectly copied. | ST#58332 |
|
Engine |
An error was encountered during the setup of Log Shipping. The error incorrectly listed the "{product name}" tag instead of "Litespeed". | ST#57785 |
|
Console |
An error was encountered when resizing or employing the minimize/maximize button on the LiteSpeed Activity screen on Win x64 platform. | ST#57031 |
The following is a list of issues known to exist at the time of this release.
|
Feature |
Known Issue |
Defect ID |
| Install and Uninstall | Remote installation for Windows 2008 fails. | ST#52244 |
|
Backup and Restore |
Mirroring for TSM is not supported. | ST#49305 |
| Users must be administrators to execute double-click restore files on Windows Vista and Windows 2008. If they are not, the restore fails. | ST#51986 | |
|
Log Shipping |
The publisher and subscriber servers must have the same version of LiteSpeed installed for log shipping to complete successfully. See Solution 45391 on SupportLink for information on upgrading log shipping plans from LiteSpeed 4.x. | ST#52230 |
|
Maintenance Plans |
Legacy native plans on SQL Server 2008 may fail due to Microsoft backward compatibility issue. See http://support.microsoft.com/kb/955626. | ST#60281 |
|
Object Level Recovery |
Object Level Recovery does not support UDT and XML SQL Server data types. | ST#46004 |
| The @onFileGroup parameter only recovers tables to the PRIMARY filegroup. | ST#44044 | |
| Object Level Recovery does not transfer the IDENTITY data type as expected. | ST#38827 | |
| The create script for check constraint uses the WITH NOCHECK option when it should use the WITH CHECK option. | ST#53043 | |
| Object Level Recovery is not able to read the backup of a SQL Server 2008 table which has FILESTREAM data. | ST#63900 | |
| Object Level Recovery UI does not support Generate DDL Scripts and Recover of Schema against table names with Japanese characters. This can be done manually using xp_objectrecovery_createscript. | ST#67463 | |
| Backups of databases using Transparent Data Encryption are not supported. | ST#66782 | |
| The following data types are not yet supported: FILESTREAM, DATE, TIME, DATETIME, DATETIMEOFFSET, HIERARCHYID, GEOGRAPHY, and GEOMETRY. | ST#66315 |
The SQL Server versions supported for log shipping depend upon the LiteSpeed release:
| SQL Server | 4.8 | 5.0.0 | 5.0.1 | 5.0.2 | 5.1 | 5.2 |
| 2000 | • | • | • | |||
| 2005 | • | • | • | • | • | |
| 2008 | • | • | • | • | • |
In addition, there are special considerations if you are upgrading from LiteSpeed 4.x to LiteSpeed 5.0.x. Review the following before upgrading from LiteSpeed 4.x to LiteSpeed 5.0 or later:
Versions 5.1 and later of LiteSpeed do not support LiteSpeed 4.x log shipping plans. If you are upgrading and have LiteSpeed 4.x log shipping plans, you must follow Solution 45391 on SupportLink to update your log shipping plans. If you do not follow these instructions, your log shipping plans will fail after the upgrade is complete.
LiteSpeed 5.x does not support SSMS plug-in functionality. However, the LiteSpeed Console allows you to read SSMS plug-in maintenance plans and upgrade them to SSIS LiteSpeed maintenance plans.
In LiteSpeed 5.x maintenance plans there are two ways to remove old backup files: the 'Clean up maintenance plans' task (which is only available for SSIS plans) and the 'Remove files older than' option in the 'Back Up Database' task. The 'Clean up maintenance plans' task removes LiteSpeed 4.8 and LiteSpeed 5.x backup files. The 'Remove files older than' option removes both LiteSpeed 4.8 and LiteSpeed 5.x backup files for legacy plans. However, for SSIS maintenance plans it only removes LiteSpeed 5.x backup files.
The timeline on the LiteSpeed Activity tab does not display activity from certain kinds of jobs if you upgrade from LiteSpeed 4.x. You can manually correct this by following Solution 45390 on SupportLink.
If receiving the message "The version of the <RepositoryDatabaseName> on server <ServerName> is greater than the version of this release of LiteSpeed for SQL Server" please see the online Help section "Upgrading Repositories and Compatibility". The message is an indication that the statistics agent on the older server does not match the newer version of LiteSpeed and must be upgraded.
Before installing LiteSpeed, ensure your system meets the following minimum hardware and software requirements:
| Operating System |
Microsoft Windows 2000 32-bit (Service Pack 4) Microsoft Windows 2003 32-bit, 64-bit (x64, Itanium) (All Service Packs) Microsoft Windows XP 32-bit and 64-bit (x64) (All Service Packs) Microsoft Windows Vista 32-bit and 64-bit (x64) (Service Pack 1) Microsoft Windows 2008 32-bit and 64-bit (x64, Itanium) (Service Pack 1) Microsoft Windows 2008 R2 64-bit (x64, Itanium) Microsoft Windows 7 32-bit and 64-bit (x64, Itanium) |
| Database Software |
SQL Server 7 32-bit (Service Pack 4) SQL Server 2000 32-bit and 64-bit (Itanium) (All Service Packs) SQL Server 2005 32-bit, 64-bit (x64, Itanium) (All Service Packs. Maintenance Plans require client tools and Service Pack 2 or later.) SQL Server 2008 RTM 32-bit and 64-bit (x64, Itanium) |
| Additional Software |
.Net Framework 2.0 or above installed before you install the LiteSpeed Console If using Tivoli Storage Manager (TSM), the TSM API and Backup/Archive Client version 5.3 or later should be installed. Microsoft Internet Explorer 6.0 or later Adobe Reader 8 to view the Installation guide |
| Processor | Follow the recommendations for the SQL Server version used. |
| Disk Space | 250 MB of disk space for installation Note: The disk space required may vary based on options selected during installation. |
| Memory | Follow the recommendations for the SQL Server version used. Note: The memory required may vary based on the following:
|
| Monitor & Resolution | SVGA with a minimum resolution of 1024x768 |
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
The LiteSpeed for SQL Server release package contains the following products:
Double-click on the installer (for instance, LiteSpeed.msi for 32-bit) and follow the on-screen directions. See the LiteSpeed 5.2 Installation Guide for full details on installing LiteSpeed. The installation guide is located on the product web site and the Quest Library. You must have Adobe Reader 8 to view the installation guide.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available, only in English, at: http://support.quest.com/pdfs/Global Support Guide.pdf.
© 2009 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656www.quest.com
Email: legal@quest.com
Refer to our Web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Imceda, LiteSpeed, and SQL LiteSpeed are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
LiteSpeed contains third party components, including SharpZipLib 0.85 and zlib 1.2.3. Copies of their licenses may be found on our website at http://www.quest.com/legal/third-party-licenses.aspx.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.