Quest® LiteSpeed for SQL Server

Version 4.8.4

Release Notes

December 6, 2007

 


Contents

 

Welcome to LiteSpeed for SQL Server 4.8.4

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations
 

Getting Started

For More Information


Welcome to LiteSpeed for SQL Server 4.8.4

 

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® databases quickly and securely. Unlike existing technologies, LiteSpeed encrypts and compresses all data as it backs it up, which means that cumbersome compression routines and poor encryption algorithms are things of the past.

 

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:

 

Note: Access to Object Level Recovery requires a Professional license.

 


New in This Release

 

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

 

Release 4.8.3

 

Release 4.8.2

 

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.

 


Resolved Issues and Enhancements

 

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.