Category
Versión del producto
Tema
Subtema
Idioma
Error "Failed to create destination folder" al ejecutar xp_restore_database usando el parametro @with. (4335160)
Error "Failed to create destination folder" al ejecutar xp_restore_database usando el parametro @with. El problema es por usar comillas dobles (") en lugar de dos comillas simples ('') con el parametro @with <p>Sustituya las comillas dobles (") por dos comillas simples ('') .<br>El script debería quedar asi:</p><p><br>exec master.dbo.xp_restore_database @database = 'testDb',<br>@filename = 'test.lbk',<br>@with ='REPLACE',<br>@with ='STATS',<br>@with ='MOVE "test1''' TO "J:\test.mdf''',<br>@with ='MOVE "test1Log'' TO "I:\test1Log.ldf''' </p>
LiteSpeed legacy licensing deprecated for SQL Server 8.9.7 (4368844)
LiteSpeed for SQL Server version 8.9.5 (and earlier versions) allows users to apply a legacy key license to register the application. ... However, if the user is using LiteSpeed for SQL Server 8.9.7 or later then a new license would need to be acquired in order to continue using the application.
What's New in Litepeed for SQL Server 8.9.7 (4368765)
A new release of LiteSpeed for SQL Server 8.9.7 is now available. ... check box is added in the Backup Template Deployment Wizard when excluding databases under the Backup Option. ... While deploying a backup template, on the Backup Options step there is an option to exclude databases in the drop-down menu.
LiteSpeed backups fail with S3 Compatible Storage MinIO (4378248)
If in LiteSpeed a Cloud Account was set up with a destination of a S3-Compatible MinIO bucket, console will confirm the connection ... But the backup jobs will fail with the following error message:
The query processor ran out of stack space during query optimization" error is encountered when creating a backup of a database with many filegroups. (4377499)
The query processor ran out of stack space during query optimization" error is encountered when creating a backup of a database with many filegroups. ... Create a large number of file groups (the issue starts manifesting at above 2000-2200 on current dev machines, but it varies with available memory)
LiteSpeed Delete Activity not deleting records from Central Database (4376872)
<br>Even with different parameters, is completed instantly without deleting any records. ... This can also happen with the LiteSpeedLocal database. ... The most probable issue is that the LiteSpeed store procedures are not registered correctly in the server where the LiteSpeed database is hosted, either the Central or the Local database.
LiteSpeed Maintenance plan cleanup history fails with error code 0xC002F210 - SQL 2022 (4376875)
SQL Server 2022 does not include ODBC driver as part of the setup. ... The ODBC driver is a LiteSpeed pre-requisite.<br> <p>Install SQL Native Client 12 </p> ... <p>https://www.microsoft.com/en-US/download/details.aspx?id=50402?1558859051</p>
LiteSpeed repository maintenance - LitespeedActivity Table (4344510)
LiteSpeed repository maintenance - LitespeedActivity Table The LitespeedActivity Database may grow too large over time and may require archiving or maintenance. ... <ul><li>Clean Up History task.
occasional backup job failures: "You are attempting to backup a database with multiple operations". (4256514)
Getting error "You are attempting to backup a database with multiple operations" when running a Fast Compression(FC) template against a database that is in restoring status. ... Would it be possible that fast compression template job skips databases in a restoring state?
How does the backup compression works in LiteSpeed for SQL Server (4376703)
Where does the backup compression takes place in LiteSpeed. ... NA During the backup process compression is done by LiteSpeed. ... A command is sent to SQL Server to perform the backup, and then LiteSpeed compresses the backup.
Subscriber Properties is showing incorrect value. (4368493)
Log shipping Subscriber is showing data incorrect even though it has been changed. ... Eg: Disconnect users is set to true but it is showing false. ... Click on the Book Icon on the top Left before Home ->Navigate to Options ->Go to Logshipping tab
Is it possible to use an AWS IAM role with the xp_slsSmartCleanup procedure, rather than an AWS access and secret key? (4306318)
Is it possible to use an Amazon Web Services (AWS) IAM role with the xp_slsSmartCleanup procedure, rather than an AWS access and secret key? <p>“IAM roles” is a global AWS cloud setting within Litespeed.<br>All Litespeed procedures should use those same cloud settings.</p>
Is it possible to set a parameter at Litespeed to divide automatically the large databases into several packages when they reach a specific size? (4329243)
This causes all backups that take longer than 180 minutes to terminate. ... Is it possible to set a parameter at Litespeed to divide the large databases into several packages so that this abort doesn't happen anymore?
Enhancement Request to have the ability to specify more than one path for the data and log files in the Automatic Restore option (4299361)
In the Automatic Restore option is only possible to select one path for the data and an another for the log files so it is not possible to use this feature if user needs more than one path <p>WORKAROUND</p>
OLR fails to start when process has more than 200 TLOG backups (4329770)
Error with OLR appears when trying to restore database + over 200 logs: ... Failed to read objects to recover. ... Error starting process 'C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\ORL.exe',Error:0xce
Restore Transparent Data Encryption (TDE) LiteSpeed Backup fails with code 995 (4224959)
When restoring a LiteSpeed backup of an encrypted database by executing T-SQL that opens the master key and executes stored procedure master.dbo.xp_restore_database with move on a SQL instance that is not the backup source, the execution fails with the following error:
Litespeed for SQL backup files deleted during backups with database in resolving state (4373101)
Backup files were getting deleted when Litespeed tried to append a differential backup to a full backup, in the following environment:<br><br>1. ... There should be an SQL Server for the AG group.
Exclusive access could not be obtained because the database is in use. RESTORE DATABASE terminated running Automated restored (4250435)
Automated restore fail during execution due DB is in exclusive Access <div>Automated restore is a subset of Steps. ... <div> </div>
slsRecast returned errors changing the backup Properties (4250465)
LiteSpeed for SQL Server Version 8.9.5.222 (64bit) Copyright 2020 Quest Software Inc. ... ALL RIGHTS RESERVED. ... The backup file is not encrypted. ... The backup file is not encrypted. ... Header info is empty.
Error 'Data source name not found and no default driver specified' when running Clean up History task in maintenance plan in SQL 2022 (4375692)
When running a Cleanup History job in a Maintenance Plan, the job doesn't run and the following error appears:<br><br>'Cleanup Backup,Maintenance plan,LiteSpeed history older than '20231207 13:23:00'<br>Msg 0, Level 0, State 0, Line 0: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified<br>Msg 0, Level 0, State 0, Line 0: [Microsoft][ODBC Driver Manager] Connection not open<br>[1] Execution Time: 0 hrs, 0 mins, 1 secs.'<br> Please ensure to download and install a SQL Server Native Client from <a href="https://www.microsoft.com/en-US/download/details.aspx?id=50402?1558859051" target="_blank">here</a> on the machine running the task, as this is required for the History Cleanup to run successfully.
The DELETE statement conflicted with the REFERENCE constraint "FK_LitespeedActivity_LitespeedDatabase (4374857)
[SQLSTATE 23000] (Error 547) ... The statement has been terminated. ... [SQLSTATE 01000] (Error 3621). ... The step failed. ... A reference value in either of the tables of the LiteSpeed Central database is corrupted and the cleanup process cannot run completely.
Amazon AWS S3 'Endpoint' option greyed out in Maintenance Plans and Backup Manager (4374591)
The 'Endpoint' field is enabled when the Region in the S3 options is set as Custom.
Object Level Restore error - 'Invalid Parameter Detected' when restoring a table (4374528)
Unable to restore a specific table with the Object Level Recovery wizard.
Configure LiteSpeed backup with SQL proxy account (4374392)
When security policies restrict access to the backup destination and requirements are not met for SQL Services backup/restore operations fail with error: "Backup of database "Database" failed.
Is there a way to ensure Transaction Log backups are not overwritten, and contain timestamps within the filename? (4374354)
Is there a way to ensure Transaction Log backups are not overwritten, and contain timestamps within the filename? ... In the Maintenance Plan, select the option 'Create unique media' at the time of taking the .TRN backups.
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