Re: Litespeed throwing deadlocks
Activity Manager likely refers to the LiteSpeed Activity Service - which you'll find in Services. It is responsible for moving data between local and central repositories. I have not seen the Deadlock...
View ArticleRe: Litespeed throwing deadlocks
Thanks David... They are disrupting my ability to use Spotlight. In Spotlight, all deadlocks errors have to be acknowledged. As a workaround, I could configure Spotlight to ignore all deadlocks, but...
View ArticleRe: Litespeed throwing deadlocks
By the way, thank you very much for following up on this. Thank you even more, if you remember to update the thread after the devs do their work.
View ArticleRe: Litespeed throwing deadlocks
Has there been any movement on this? Every time I open Spotlight, I have to go to each server and acknowledge all of the deadlocks. Because there are so many, I can't look at each deadlock...
View ArticleRe: Litespeed throwing deadlocks
If I turn off the central repository, will it temporarily resolve this issue?
View ArticleRe: Litespeed throwing deadlocks
That would probably do it, but turning the central "off" would require rerunning instance configuration on each server that is reporting. Optionally, you could try disabling the LiteSpeed Activity...
View ArticleRe: Litespeed throwing deadlocks
Thanks, I will try just disabling the service. LiteSpeed is version 7.0.4.2Spotlight on SQL Server Version: 9.0.1.6197
View ArticleRe: Litespeed throwing deadlocks
Ok, I tried disabling the Litespeed Activity service... now, every time it attempts to backup a log file (every 15 minutes), Spotlight shows an error in the Services panel: "The SQL Agent Job...
View ArticleRe: Litespeed throwing deadlocks
Rob, if you rerun instance configuration and stop the instance reporting to the central, I think that will stop the issue temporarily. Dev is working on a solution, but I don't have a firm delivery...
View ArticleRe: Litespeed throwing deadlocks
Thanks David, I have submitted the support request as instructed. -Rob
View ArticleLog Reader Question
At some point in time not too long ago, someone discovered that data had been changed in a table in a database. Using a lot of trial and error, I eventually used log reader to determine all kinds of...
View ArticleRe: Log Reader Question
Microsoft does not track user information in transaction logs. LiteSpeed may be able to show this information if the session is active at the time the information is reviewed. But for historical log...
View Articlenew version LiteSpeed SQL SERVER 7.1 released?
Was the new 7.1 version released ? If so, can you please provide the link for download. I can just see 7.0.4 version in download window.
View ArticleRe: new version LiteSpeed SQL SERVER 7.1 released?
LiteSpeed for SQL Server 7.1 will be released tomorrow, by 5pm ET. Please look for a blog post on this site with a list of new features later today. Thanks.
View ArticleLiteSpeed impact on msdb database?
We have a customer who wants to use LiteSpeed for backup process on few SQL Server 2008 EE machines. We have to deploy our product and we are considering system database sizing. What impact LiteSpeed...
View ArticleRe: LiteSpeed impact on msdb database?
LiteSpeed doesn't use msdb. SQL Server uses it to store backup history and jobs no differently than if you did native backups. We don't typically size msdb as the databases tend to be small.LiteSpeed...
View ArticleRe: LiteSpeed impact on msdb database?
LiteSpeed can be configured to store log activity in LiteSpeed Local as default, msdb or custom database, right? So you are saying that in any configuration scenario LiteSpeed doesn't use SQL server...
View ArticleRe: LiteSpeed impact on msdb database?
SQL Server stores backup activity in msdb. Those backups are actually LiteSpeed backups, but the VDI API from Microsoft makes backups appear to SQL Server as though they were native. LiteSpeed will...
View ArticleRe: LiteSpeed impact on msdb database?
Thanks David, these are enough information for our team so we can discuss it with the customer.Regards
View Article