Category
Versión del producto
Tema
Subtema
Idioma
Mininium permissions needed to run LiteSpeed for SQL Server. (4348514)
What are the minimum permissions (NTFS and Shares) need to be granted to a LiteSpeed for SQL Server user and on what files/directories? ... NOTE: At the least, the LiteSpeed user needs Read and Write access to:
Restores are slow without changes in DB size or change in script. (4220589)
Time to complete restore process has become slow without any significant changes to the size of database or adding a MOVE command to the restore. ... SQL Server error log will display an error: BobMgr::GetBuf: Bob write not complete after 60 seconds.
The verify of the backup file is slow (4220466)
A maintenance plan that includes a backup and verify cannot complete within the maintenance window. ... How do you backup and verify the file? ... Verify process may take an extended time, depending on the size of the database and individual environment.
Start/end time is changed arbitrarily when the restore interval is changed in a log shipping plan (4254790)
Start/End time is changed arbitrarily when the restore interval is changed via log shipping plan options <div>The default setting of the restore offset to end at 11:59PM.</div><div>So when is changed the end time to whatever and then edit the restore job via the logshipping wizard the default end time is reset to 11:59PM for the restore offset.</div><div></div> <p>enhancement request (LS-2288) has been created to address this behavior</p><p></p><p>Workaround</p><p>Edit the Interval values via SSMS rather than the log shipping wizard when a custom time window is set that it's your case.</p><p>Please note: "occurs every" in SSMS = "restore interval" in Logshipping options</p> LS-2288
How does LiteSpeed calculate the compression? (4223127)
In completion message and in the Status Reports, LiteSpeed indicates the amount of compression; how is this figure calculated? ... Compression % = 100 - (Backup Size / DB Size)*100 ... For a full back up, the DB size is the sum of the database size and the log files.
Find LiteSpeed license number using comand line (CLI) (4313336)
How to find license number in case the user does not have local administrator rights for LiteSpeed Graphic User Interface (GUI). ... Local windows administrator rights are needed to view the licensing information through the LiteSpeed GUI.
How can Litespeed leverage S3 acceleration enabled endpoint (4329385)
Select 'Use Amazon S3 Transfer Acceleration Speed' to use Amazon's S3 Transfer Acceleration feature which allows for increased upload speed to S3 storage up to 200% in some cases by using local CloudFront endpoints
Column names in each table must be unique. Column name 'PID' in table 'dbo.LiteSpeedActivity' is (4223016)
Error message appears when the Local (or client) installation is a different version than the version on the server holding the Central Repository database or the installer is attempting to update a table with the column already defined:
Litespeed recommendations when using Antivirus (4319430)
There are some antivirus functions that can be troublesome for Litespeed activities. ... If some exclusions are not included at the level of the antivirus this could lead in the interruptions of the Litespeed activities like fail of the jobs or slow performance in some cases, because the antivirus will be analyzing the Litespeed files or even the backups files.
Automated Restore feature is available only with Enterprise Edition (4293028)
The following message is displayed: ... LiteSpeed® for SQL Server® Version 8.9.1.302 (64bit) Copyright 2020 Quest Software Inc. ... ALL RIGHTS RESERVED. ... [SQLSTATE 01000] (Message 1) ... This feature is available only with Enterprise Edition [SQLSTATE 42000] (Error 62003)
How to run SQL Profiler on SQL Server 2005. (4231695)
Creating SQL Server 2005 trace file for troubleshooting purposes for LiteSpeed, Quest Central for SQL Server and database applications supported on SQL Server 2005. ... A SQL Profiler traces databases activities and save the report in different formats.
Requested the option to "force a full backup if one has not been taken" be added as an option for tlog backups created via a backup template (4333589)
T-log is set up via template. ... When a new database is created, LiteSpeed does not force a new full backup and it fails as there is not one. ... Would it be possible to force a full backup when there is not one already?
An error occured when attempting to detect if LiteSpeed was installed on <nameof the instance& (4264545)
The folllowing error may display during installation, running LiteSpeed backup or running xp_sqllitespeed_version ... There could be an alias or host file entry on the host or client machine that is set incorrectly and pointing to the wrong server or IP address, which in turn can lead to a connectivity failure.
Error: Error 23 (Data error(cyclic redundancy check).) (4351896)
This is a hardware disk drive malfunction so please replace with a working hard drive.
Restoring an entire lost SQL Server from LiteSpeed's database backups (4252283)
We have entirely lost a SQL server. ... And we are trying to restore it using our LiteSpeed for SQL Server backups. ... It appears that we need to restore the Master database first, and that we need to do that from the command line.
Fast Compression task in a Maintenance Plan has no Always On Availability Group options for backup of secondary replica, or the preferred replica. Only primary replica or none (4240084)
It only has options to backup primary replica or none. ... (FC configured from the Backup Wizard also has the same limitations) ... We would like to use FC AlwaysOn backup to the secondary replica, or the preferred replica as specified in the Availability Group, like the regular 'Back Up Database' task does allow.
SmartCleanup not working correctly (4300088)
Smartcleanup, when used with the parameter “@Locations”, will fail to delete backups if the path in that parameter contains a variable. ... Create a job to delete the backups ... STATUS ... Issue fixed in version 8.9.5.247.
LiteSpeed Developer Edition - is Object Level Recovery available? (4218726)
LiteSpeed Developer Edition - is Object Level Recovery available? <br>Developer Edition uses bpc to restore table level data, so the schema would need to be in place, prior to executing (the table itself would need to be created/restored, then the data restored via LiteSpeed).<br><br>In order to restore the table and the related data using LiteSpeed, the LiteSpeed Professional version would be recommended.<br> LiteSpeed Developer Edition<br/>SQL Server 2000 & 2005
How do we create a Log Shipping plan using LiteSpeed? (4251759)
How to configure Shipping. How do we create a Log Shipping plan using LiteSpeed? <p>The 'Configure Log Shipping Guide' (attached) has the configuration steps. The entire document is very useful information to have and the key part you are looking for would be the section 'Create Log Shipping Plans' on page 8.</p><p>And better than that, also attached is a PowerPoint training (with configuration screenshots starting on slide 9) for Technical Support regarding log shipping with LiteSpeed.</p><br>
Backup transaction log with option TRUNCATE_ONLY does not create backup file (4351902)
The simple recovery model should be used to automatically truncate the transaction log.</span></p> For additional information, see<span><a href="http://msdn2.microsoft.com/en-US/library/aa933082(SQL.80).aspx">http://msdn2.microsoft.com/en-US/library/aa933082(SQL.80).aspx</a></span><p><span>AUTO_SHRINK only reduces the size of the transaction log if the database is set to SIMPLE recovery model or if the log is backed up.</span><span>The AUTO_SHRINK option causes files to be shrunk when more than 25
Error: "Invalid Login Details for : [ServerName] Provider cannot be found...." (4351747)
Provider cannot be found. ... It may not be properly installed." ... SQL LiteSpeed uses OLEDB to make connections to the database. ... There is likely an OLEDB configuration problem or a bad installation of OLEDB.
Can a database in suspect mode be backed up? (4223198)
Database is in suspect or emergency mode. ... Can a native SQL Server backup or LiteSpeed backup be ran for Full, Differential or Log backup? ... A database can be marked for many reasons: ... - A database or log file is missing.
Error: "Failed to set data for StatsEnabled" when closing the Enterprise Console. (4238060)
On an operator's computer where only the LiteSpeed Client has been installed and the operators are not Local Admins and error is continuously received when the operator tries to close Enterprise Console:
LiteSpeed Enterprise Console does not recognize SQL 2005 instance as running (4341954)
LiteSpeed is not picking up SQL 2005 on the computer where both SQL 2000 and SQL 2005 severs are installed. ... An error is received when attempting to register the new server, even when LiteSpeed was installed after SQL server 2000 and 2005 were already in place.
How does LiteSpeed update the LiteSpeed Local and Central repositories? (4224909)
What is the process to have LiteSpeed activity update to the Local and Central Repositories? ... LiteSpeed 2005 can collect and retain statistics on backups occurring through the LiteSpeed 2005 Engine from the GUI, command line, or extended stored procedures, including backups completed by native SQL Server.
Asociación de nuevos productos
- Herramientas de autoservicio
- Base de conocimientos
- Notificaciones y alertas
- Soporte de productos
- Descargas de software
- Documentación técnica
- Foros de usuarios
- Tutoriales en video
- Aviso de actualizaciones de páginas web (RSS)
- Comuníquese con nosotros
- Soporte Técnico
- Ver todos