Release Notes
January 2017
These release notes provide information about the LiteSpeed Engine for SQL Server release.
LiteSpeed Engine for SQL Server is a complementary technology to LiteSpeed for SQL Server product. LiteSpeed Engine for SQL Server allows seamless data compression and encryption without having to modify existing SQL scripts.
By providing LiteSpeed’s compression and encryption functionality in a driver based solution, users can continue using native or third party backup tools, while getting the full advantage and flexibility of LiteSpeed’s time and space saving features.
The LiteSpeed Engine solution consists of two parts, which are both installed by default:
File driver component—This does the actual work of compressing and optionally encrypting your SQL Server database backups. It works by intercepting the backup file stream and compressing the results before reaching the actual physical disk. If restoring a database, the operation is reversed – the file stream is decompressed before reaching SQL Server.
Once installed and configured, the driver will work transparently in the background, compressing and decompressing and optionally encrypting and de-encrypting your SQL Server backups and restores.
Added support for ANSI, UTF-16LE, and UTF-16BE.
New and improved database backup compression algorithms that offer even better CPU usage and compression characteristics. See the User Guide for more information about the compression levels.
LiteSpeed Engine automatically scans and hooks available drives on startup. Now, if a cluster drive failed over or a USB drive was added since startup, you can manually rescan the disk devices using the new File | Driver Management | Rescan Drives option to be able to do compressed backups to these drives.
Now you can view the LiteSpeed engine status in the Configuration Editor status bar and in the file menu (File | Driver Management | Driver Status). New Driver Status dialog allows you to stop and start the driver and configure tracing options.
When driver tracing is enabled, trace information for multiple activities continuously appends. You can now easily clear the log by selecting File | Driver management | View driver tracing and clicking Clear. Also, you can click Refresh to see the latest log entries.
The following is addressed and implemented in LiteSpeed Engine 2.0.3.
Table 1: UI resolved issue
| Resolved Issue | Issue ID |
|---|---|
| "Object reference not set to an instance of an object" error can be generated when the LiteSpeed Engine Configuration Editor is closed. | ST103460 |
The following is addressed and implemented in LiteSpeed Engine 2.0.2.
Table 2: Restore resolved issue
| Resolved Issue | Issue ID |
|---|---|
| In certain cases, LiteSpeed Engine for SQL Server may return an error or possibly cause a system fault during a restore operation when the backup is larger than 4 GB. | ST81145 |
The following is addressed and implemented in LiteSpeed Engine 2.0.1.
Table 3: Restore resolved issue
| Resolved Issue | Issue ID |
|---|---|
| LiteSpeed Engine 1.1 backup cannot be restored with LiteSpeed Engine 2.0, if the index embedded within the backup contains more than 3300 entries. | ST79890 |
The following is a list of issues addressed and enhancements implemented in LiteSpeed Engine 2.0.0.
Table 4: Various resolved issues
| Resolved Issue | Issue ID |
|---|---|
| General - Removable backup media is not supported. | N/A |
| General - LiteSpeed Engine cannot restore LiteSpeed for SQL Server backups. | ST68737 |
| Extensions - Backup file extensions can now contain Unicode characters. | ST69591 |
| Driver Tracing - Add the Rescan Drives option results to the trace log. | ST77795 |
| Support Bundle - Support Bundle sometimes cannot be unzipped using WinZip. | ST69196 |
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
Table 5: General known issues
| Known Issue | Issue ID |
|---|---|
| LiteSpeed Engine is not cluster aware. It should be installed on a local drive only. | ST78492 |
| When working with disks utilizing sector sizes other than 512-byte, LiteSpeed Engine cannot not take advantage of sector aligned file I/O. Users may witness a performance decrease in LiteSpeed Engine as a result of using disks that are of a different sector size. | ST68054 |
Table 6: Uninstall known issues
| Known Issue | Issue ID |
|---|---|
| Uninstall - After uninstalling LiteSpeed Engine for SQL Server, the server should be re-booted. | N/A |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy
