Quest® LiteSpeed
Version 4.8.4
Release Notes
December 6, 2007
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.
LiteSpeed
is the new way of backing up SQL Server
The size of the backup file is typically only a fraction of the size of the original backup size, maximizing storage efficiency and ensuring significant savings in disk space. The encryption algorithm ensures that data cannot fall into the wrong hands as it is transported to an off-site backup facility.
Down time and database failures are a reality. Components fail, databases become corrupted, and administrators make mistakes. But by using LiteSpeed, restore time can be reduced and downtime minimized. Mission critical databases can be brought back online quickly and reliably using LiteSpeed’s revolutionary new technology.
Key Benefits:
Reduced Storage Requirements (up to 95% compression)
Reduced Backup Times (up to 75% faster than native SQL Server)
Reduced Restore Times
Increased Transaction Throughput
Secure Backup Device Files (256-bit encrypted)
Reduced Network Load
Fully Integrated into SQL Server
Highly Tunable
User-definable Compression Level
Choice of Encryption Method: RC2 (40-bit, 56-bit, 112-bit, 128-bit), RC4 (128-bit), 3DES (168-bit), AES (128-bit, 192-bit, 256-bit)
Note: Access to Object Level Recovery requires a Professional license.
Several new features have been added or modified to increase productivity and functionality of LiteSpeed for SQL Server 4.8.4.
Release 4.8.4
Users with existing SSMS plug-in created jobs can now upgrade their old version jobs to the current version using the conversion wizard.
The default logging path is now C:\Documents and Settings\All Users\Application Data\Quest\Litespeed, instead of x:\Program Files\Imceda\LiteSpeed\SQL Server\Engine\Logs.
LiteSpeed 4.8.4 offers partial support for SQL Server CTP 4 and Windows 2008 R0.
Supported features include: xp_backup_database, xp_restore_database, xp_backup_log, xp_restore_log, xp_sqllitespeed_version, xp_restore_filelistonly, xp_restore_headeronly, xp_restore_verifyonly and scheduling backups and restores via the Enterprise Console.
Unsupported features include (in particular) the MMC console, SQL Server clusters, Object Level Recovery, the SSMS Plug-in, Tivoli Storage Manager (TSM), and log shipping.
The OLR process does not work with SQL Server 2008 CTP 5. If initiated, the OLR process must be killed through the Task Manager.
Release 4.8.3
Localized for English.
SQL Server 7 supported.
The Red Server Icon has been redesigned with no change in function.
The Orange Server Icon (for Reporting) appears in the Enterprise Console Tree if LiteSpeed cannot tell whether SQL Server is running.
Release 4.8.2
Localized for Japan.
Release 4.8.1
Fixes a 4.8 issue on x64 and Itanium versions of LiteSpeed that caused restores to fail on backup files that were larger than 4GB.
Release 4.8
The Red Server Icon (for reporting) appears in the Enterprise Console Tree if a server or database has previously been backed up using LiteSpeed, but there are no recent backups for that server or database (that is, no records of backups exist in the central repository). This icon appears if there are no backups within three days of the last backup and may indicate a problem with the server or the LiteSpeed Activity Service.
Creating Partial Backups
To create a partial backup, use the BACKUP statement and specify the READ_WRITE_FILEGROUPS option. You can also specify any read-only file or filegroup to include it in a partial backup.
The required syntax for creating a partial backup is:
BACKUP DATABASE database_name
READ_WRITE_FILEGROUPS [ , <file_filegroup_list> ] TO <backup_device>
According to SQL Server 2005's documentation, to cause a partial backup enter:
@read_write_filegroups=1
Note: For additional information refer to Microsoft's SQL Server documentation:
http://msdn2.microsoft.com/en-us/library/ms191539.aspx
Object Level Recovery Execute SELECT:
Prior to LiteSpeed 4.8, if the destination table already existed you received the error message: 'Failed to create table'. This required the creation of a new table for every query. Thus to create a UNION of SELECT results, it was necessary to CREATE and DROP a temporary table and then move the rows to the more persistent table.
Beginning in LiteSpeed 4.8, if the destination table already exists and is equivalent in structure to the query results, then the rows are inserted into the existing table. For equivalence, the column names of the table and of the query results are not required to be equal, rather the number of columns and the details of the data types of each column are required to be the same. If the table and query results are not equivalent, then the error message 'Existing table <table name> is not equivalent to query results.' is returned. If OLR is unable to accomplish the comparison, the message is 'Unable to describe existing table <table name>.'
Object Level Recovery on Differential Backups:
Object level recovery commands can now be used on differential backups in addition to full backups.
Encryption is now available with both Standard and Professional licenses.
The following is a list of issues addressed and enhancements implemented in the LiteSpeed for SQL Server 4.8.4, 4.8.3, 4.8.2, 4.8.1, and 4.8 releases.
|
Resolved Issue |
Resolved in Version |
Change Request |
|
LiteSpeed Defaults has wrong name in the Japanese-language Start menu. |
4.8.4 |
38,960 |
|
Maintenance plans created with the SSMS plug-in drop the first minute value if it is zero. |
4.8.4 |
38,956 |
|
LiteSpeed Defaults dialog box is incorrectly translated into Japanese. |
4.8.4 |
38,954 |
|
LiteSpeed SSMS plug-in contains non-translated strings in Japanese version. |
4.8.4 |
38,942 |
|
Files attached to Differential or Transaction logs backups are not shown in the Enterprise Console restore wizard. |
4.8.4 |
0228138 |
|
Maintenance plans created with the SSMS plug-in drop the first minute value if it is zero. |
4.8.4 |
0228011 |
|
xp_restore_checksumonly hangs when run via QA or command line. |
4.8.4 |
0227624 |
|
The LiteSpeed Enterprise Console incorrectly adds the @OLRMAP parameter to TSM Backups. |
4.8.4 |
0227382 |
|
If a database is being backed up in a maintenance plan, and the name of the database is changed, the backups fail but are still reported as success. |
4.8.4 |
0227476 |
|
"Activity logging", "Activity Data", and "Activity" are translated wrongly. |
4.8.4 |
0227011 |
|
LiteSpeedDefaults does not read setting on remote computers. |
4.8.4 |
0226710 |
|
Backup with attached files fails if the file being attached is opened with a program that maintains a lock on the file. |
4.8.4 |
0226286 |
|
A maintenance plan created with the SSMS plug-in to backup all user databases doesn't recognize new databases. |
4.8.4 |
0226095 |
|
Extractor utility would not function properly on backups created with compression level 2 or greater. |
4.8.4 |
0225741 |
|
Add expiration date of key to success/failure message. |
4.8.4 |
0225498 |
|
Percentage for failed column does not have correct column title in success/fail by database report. |
4.8.4 |
0225466 |
|
Translation for OK/Cancel dialog does not follow MSSQL terminology on Extend stored procedure wizard. |
4.8.4 |
0225465 |
|
LiteSpeed Enterprise Console does not pass the proper syntax for backups to tape. |
4.8.4 |
0225392 |
|
Job not created when Email Operator Notification is selected in a Maintenance Plan (tasks are not displayed). |
4.8.4 |
0225269 |
|
Password field is not grayed out when using Windows Authentication for a double click restore. |
4.8.4 |
0225263 |
|
SQL Authentication password field grayed out when using Log Shipping Wizard. |
4.8.4 |
0225217 |
|
Media family incorrectly formed error when attempting to restore SLS full with native TLOG files using Restore Database (non-wizard). |
4.8.4 |
0224556 |
|
OLR Restore Table & Create Script unable to restore to a .able with a dot (.) in the name. |
4.8.4 |
0224555 |
|
LiteSpeed Enterprise Console should log "Failed Maintenance Plans" in the event any part of the job step reports failure. |
4.8.4 |
0224554 |
|
Object Recovery Wizard "Add Backup Files" ellipses button is not viewable. |
4.8.4 |
0224552 |
|
Enterprise Console TreeView does not show all user tables. |
4.8.4 |
0224477 |
|
Error when running a restore if the SQL user account's default database is the same as the database you are trying to restore. |
4.8.4 |
0224317 |
|
LiteSpeed Enterprise Console does not script the needed syntax for user specified buffer count. |
4.8.4 |
0224302 |
|
Rename For Last Day report schedule option to Last 24 Hours. |
4.8.4 |
0224236 |
|
DoubleClick restore dialog hangs if the database contains hundreds of datafiles. |
4.8.4 |
0224099 |
|
LiteSpeed Enterprise Console does not pass the restore attached file syntax when restoring from TSM. |
4.8.4 |
0224097 |
|
LiteSpeed Maintenance plans fail to function when specifying a database with a space at the end of the name. |
4.8.4 |
0224096 |
|
Ability to do TSM backup and mirror the file. |
4.8.4 |
0224089 |
|
Scheduled jobs should create file names of run time, not create date/time. |
4.8.4 |
0223958 |
|
Maintenance plan with 40-bit encryption loses check box next to "secure backup with encryption". |
4.8.4 |
0223487 |
|
SLA Report Detail Backup report shows garbage characters in Japanese version. |
4.8.4 |
0222974 |
|
SLA Report Backup Job Status report shows garbage characters in Japanese version. |
4.8.4 |
0222971 |
|
SLA Reports shows garbage characters in Japanese version. |
4.8.4 |
0222969 |
|
Japanese translation for "Data Transformation Services" does not follow MS SQL terminology. |
4.8.4 |
0222962 |
|
Japanese translation for label in OK/Cancel dialog does not follow MS SQL terminology. |
4.8.4 |
0222961 |
|
Extract to multiple directory capability for the extractor utility. |
4.8.4 |
0220808 |
|
'Incorrect syntax near 's' dump when creating a Maintenance Plan with an apostrophe in Enterprise Console. |
4.8.4 |
0220725 |
|
OLR Create Script - SQL2005 - PRIMARY KEY and UNIQUE KEY columns of the NONCLUSTERED type are completely missing. |
4.8.4 |
0220426 |
|
OLR Create Script - SQL2005 - PRIMARY KEY and UNIQUE KEY columns of the CLUSTERED type are sometimes in the incorrect order. |
4.8.4 |
0219091 |
|
Allow users to specify TSM estimated size with the xp_backup_database stored procedure. |
4.8.4 |
0216688 |
|
Files from successful MP backup removed even if entire MP doesn't complete successfully. |
4.8.4 |
0215076 |
|
SSMS Plug-in is not installed if SQL Client Tools are not in the C directory. |
4.8.4 |
0213798 |
|
LiteSpeed SSMS Maintenance plans created on LiteSpeed 4.7 are not upgraded when installing LiteSpeed 4.8. |
4.8.4 |
0212316 |
|
-ioflag parameter not passing in to slssqlmaint when run in a job. |
4.8.4 |
0204149 |
|
OLR Restore Table and Create Script: Unable to restore or script a table that has a dot (.) in its name. |
4.8.3 |
0222636 |
|
SQL Server 7 support reintroduced with Windows 2000. |
4.8.3 |
0222467 |
|
Long Reports from Statistics contain truncated strings. |
4.8.3 |
0222291 |
|
Running multiple xp_sqllitespeed_licenseinfo procedures in parallel could cause undefined behavior. |
4.8.3 |
0222203 |
|
Maintenance plan does not fail if one backup fails but the last backup succeeds. |
4.8.3 |
0221569 |
|
'remove files older than' parameter in Enterprise Console MP causes step to report success when it actually failed. |
4.8.3 |
0216841 |
|
Allow DoubleClick restores created on 4.8.3 X64 systems to be restored using X86 systems. |
4.8.3 |
0216662 |
|
SSMS Plug-in does not function on SQL Server 2005 SP2. |
4.8.3 |
0208517 |
|
SLS SSMS plug-in maintenance plan conversion feature fails to convert plan. Failure produces error message. |
4.8.3 |
0201210 |
|
Registry entries did not populate properly in 64-bit install. |
4.8.2 |
0219083 |
|
Maintenance plan and job failures do not show up in Enterprise console. |
4.8.2 |
0217507 |
|
READ_WRITE_FILEGROUPS clause should be usable with the xp_restore_database stored procedure. |
4.8.2 |
0216651 |
|
Using Backup mirroring with the OLR map parameter causes a "System Exception " message. |
4.8.2 |
0217328 |
|
Attached files do not show in the Restore Wizard Summary screen. |
4.8.2 |
0218975 |
|
OLR fails on Partitioned tables. |
4.8.2 |
0212612 |
|
On x64 and Itanium versions of LiteSpeed for SQL Server, restores to fail on backups that were larger than 4GB. |
4.8.1 |
0216562 |
|
LiteSpeed Compression now utilizes the 64-bit zlib library. This can increase compression performance on x64 systems. |
4.8 |
0203558
|
|
Xp_LiteSpeedVersion_Info can now be obtained by Right Clicking on a server node and choosing "License Info". |
4.8 |
0185716
|
|
DTS Stats are now multi threaded. |
4.8 |
0195863 |
|
SLSSQLMAINT now has a proper help function that can be accessed by using the command slssqlmaint -?. |
4.8 |
0196214
|
|
SQL Servers did not show up red when under a group. |
4.8 |
0204132 |
|
Throttle was incorrect for multicpu systems. |
4.8 |
0197107 |
|
Moving SQL Server 2005 named instances from one named group to another could generate an error message. |
4.8 |
0206079 |
|
SLS Backups and Restores cannot be scheduled from the NON-WIZARD backup option. |
4.8 |
0199249
|
|
Tape Restore Performance has been improved. |
4.8 |
0203477 |
|
Point in time restore in enterprise console does not include seconds in the selected time. |
4.8 |
0195314 |
|
lsm temp file generation temp directory command now gives a proper error if it does not exist. |
4.8 |
0206658 |
|
The TSM Management Class is now supported in the LiteSpeed Enterprise Console. |
4.8 |
0196218
|
|
Logging=3 can now be set from the backup options screen in Enterprise Console, command line, or registry entry.
|
4.8 |
0195267 |
|
Job and DTS stats were being figured based of the time modified and not the time created, this would cause Stats to be shown incorrectly. |
4.8 |
0204130 |
|
Enterprise Console could produce an error message when you attempt to add a server through the tree view. |
4.8 |
0207046 |
|
Users may now run a log backup with no recovery. |
4.8 |
0203560 |
|
Last Backup Time could come from a deleted database. |
4.8 |
0205945
|
|
Logshipping GUI would automatically insert a comma separator if the restore interval was set greater than 1000. |
4.8 |
0207341 |
The following is a list of issues known to exist at the time of LiteSpeed for SQL Server 4.8.4 release.
|
Known Issue |
Change Request |
|
LiteSpeed incorrectly writes successful backup details to the SQL Server error log or event viewer if DBCC TRACEON (3226) is run with the backup. |
38.972 |
|
If backing up to a root directory, the maintenance plan backup will fail if the root is specified with \(C:\) rather than with C: |
38,970 |
|
A LiteSpeed differential backup maintenance plan does not remember settings if the 'Use LiteSpeed for SQL Server' Backup Option is unchecked. |
38,959 |
|
The UNLOAD parameter does not work when used with xp_restore_verifyonly. |
38,924 |
|
Restoring some but not all attached files completes but the process hangs and does not end. |
38,853 |
|
The Enterprise Console Remote Installation Wizard generates a stack dump if the selected .msi path is invalid. |
38,805 |
|
OLR stack dump occurs if Finish button is selected before bulk copy process is complete |
38,971 |
|
Processor/affinity details are incorrectly returned from the LiteSpeed engine. |
38,969 |
|
Differential backup LiteSpeed maintenance plan does not remember setting if you uncheck 'Use LiteSpeed for SQL Server' backup options. |
38,959 |
|
Done button not available in Edit Connection Properties window when performing SSMS plug-in native Maintenance Plan conversion. |
38,952 |
|
A bug with MDAC can cause the DbMaintStatus query to be malformed. |
38,951 |
|
If the MSDB table is not updated after backup successfully completes, the backup file is deleted. |
38,945 |
|
Object Level Recovery does not restore the Identity clause when recovering data. |
38,827 |
|
oledbdo.dll and slsreg.exe files are not being removed after uninstall. |
38,790 |
|
Attempting to restore multiple transaction logs from TSM using the Enterprise console fails with error message. |
38,796 |
|
'Backups in progress' statistic not showing activity. |
38,809 |
|
Scheduling a job from the Backup or Restore wizard fails if the IP address is used as the instance name. |
38,848 |
|
Multiple backups with the exact same start time can cause 'databases with backups' and 'databases without backups' to be wrong. |
38,654 |
|
The SSMS plug-in is not fully uninstalled if LiteSpeed is uninstalled from a system running X64\X86 side by side. |
38,691 |
|
Jobs run at Midnight do not appear in the status report. |
38,712 |
|
The Enterprise Console Restore Wizard incorrectly identifies DIFFERENTIAL backups appended to the same file created with the NON-Wizard Backup option. |
38,692 |
There are no known third party issues at the time of LiteSpeed for SQL Server 4.8.4 release.
LiteSpeed log shipping is not compatible with SQL Server 7.
Clustered systems using encryption under LiteSpeed versions 4.8.2 and before can encounter maintenance plan issues. Customers having the Cluster+Encryption configuration should upgrade to LiteSpeed 4.8.3 or later.
RC2 encrypted backups created on systems running Windows 2000 can intermittently fail to decrypt on non-Windows 2000 systems. A Microsoft article describing this issue in greater detail can be found at the following location: http://www.support.microsoft.com/kb/841715. Quest Software recommends that Windows 2000 systems use 3DES and above for backup encryption.
Users upgrading from version 4.0 or previous builds may be asked to reboot – no reboot is required.
LiteSpeed SSMS plug-in functionality is available on SQL Server 2005 build 9.0.3042.1 and above. All other SQL Server 2005 versions are unsupported.
Before installing LiteSpeed for SQL Server 4.8.4, ensure your system meets the following minimum hardware and software requirements:
| Operating System |
Microsoft Windows 2003 (All Service Packs) Microsoft Windows 2000 (Service Pack 4) Microsoft Windows XP (Service Pack 1) | |||||
|
Database Software |
SQL Server 7 (Service Pack 4) SQL Server 2000 (All Service Packs) SQL Server 2000 64-bit (Itanium) (All Service Packs) SQL Server 2005 (All Service Packs, x86, x64, and Itanium) (SSMS plug-in requires SP2 and above) | |||||
|
IBM Tivoli Storage Manager |
Required
Not Required
|
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 release is localized to the following languages: Japanese.
This release has the following known capabilities or limitations: Log Reader was not translated.
The LiteSpeed for SQL Server 4.8.4 release package contains the following products:
|
1. |
"LiteSpeed.msi" |
|
32-bit installer |
|
2. |
"LiteSpeed-x64.msi" |
|
64-bit installer |
|
3. |
"LiteSpeed-IA64.msi" |
|
Itanium 64-bit installer |
|
4. |
"SLS Classic.msi" |
|
Developer Edition installer |
The Installation Guide, with full details on installing LiteSpeed, is contained on the website and the Quest Library. It is called LiteSpeed 4.8.4 Installation Guide.
Double-click on the installer (for instance, LiteSpeed.msi for 32-bit) and follow the on-screen directions. See the Installation document for full details on installing LiteSpeed.
After the installer has been run, LiteSpeedHelp.chm is in the directory where LiteSpeed for SQL Server 4.8.4 has been installed.
| 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 do the following:
View the Global Support Guide for a detailed explanation of support
programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global
Support Guide.pdf.
This document 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.
© 2007 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT 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.
This product includes software developed by:
JVCL source code that can be obtained from http://jvcl.sourceforge.net
SynEdit source code that can be obtained from http://synedit.sourceforge.net
Virtual Treeview source code that can be obtained from http://www.delphi-gems.com
The Delphi toolbar, which is copyright
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 92656 Email: legal@quest.com |
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.