SQL Litespeed
Apr 5, 2004Hi,
Is anyone using SQL lite speed here?
If so what are your opinions on it? is it worth it?
Cheers
Hi,
Is anyone using SQL lite speed here?
If so what are your opinions on it? is it worth it?
Cheers
Does anyone use Litespeed with a 64 bit environment (64 bit Windows 2003 server, 64 bit SQL Server)? Is it compatible, or do you have to by a 64 bit version of Litespeed? Also, any good links on this stuff would be great.
Thanks in advance.
Future guru in the making.
Has anyone used SQL Litespeed .We have 1 TB database and moving to different location so we want it to be done fast. How is compression ratio of backup files and how does it work with SQL server 2005? Is it easy to install in Production environment. How much does it cost?
Please experts, Throw some light.
Anyone have experience with either of these products? Your thoughts?
-a
I am trying to Repaire my logship by setting it up again with the logship wizard.
I get the following error.
How can i remove the old logship plan ?????
Unable to successfully add subscriber for svs022ezissql2 and EZIS_LOGSHIP due to Unable to successfully execute SLS_LogShipping_AddDatabase for subscriber!
Error: SLS_LogShipping_AddDatabase failed. msg: Database is already part of a log shipping plan on subscriber!
Plan failed to install. Removing plan.
Successfully executed SLS_Remove_Plan.
I am trying to setup logship. I am getting the error while running the following script. I got this script from the Logship wizard. And it is not mine. This is the secondary server. Primary server script ran fine.
Exec dbo.SLS_LogShipping_AddServer
@PlanID= null,
@PlanName='LogShipDataBaseName',
@ServerName='Servername',
@DestinationType=0
GO
The error message is
Msg 50000, Level 16, State 1, Procedure SLS_LogShipping_AddServer, Line 671
failed to add a server.
msg:Check for Subscriber on Subscriber failed.
I am getting this error after Litespeed installed:
Error Msg: SQL Server could not read the registry value: HKLMSoftwareImcedaSQLLitespeedexepath.
Check that the value exists, and that the SQL Server service account has full access to this keyºlue.
(11200)
Anyone gotta help here, thanks a lot.