Re: Transaction Log Backup Failing as Deadlock Victim

Newsgroups	comp.databases.ms-sqlserver
Date	2014-01-28 16:58 -0800
References	<a226b43d-9e59-4686-b21c-b818fed76ef8@googlegroups.com> <XnsA2C3E928BBD6BYazorman@127.0.0.1>
Message-ID	<06522420-91a7-4905-8d4b-9d397a3eed68@googlegroups.com> (permalink)
Subject	Re: Transaction Log Backup Failing as Deadlock Victim
From	rja.carnegie@gmail.com

Show all headers | View raw

On Tuesday, 28 January 2014 21:55:13 UTC, Erland Sommarskog  wrote:
> Supposedly, it is not the T-LOG backup itself that fails, but what fails
> is when the log backup is recorded in msdb, which is not known for its
> optimal indexing. This blog post with a script from my fellow MVP Geoff
> Hiten should help you.

Is this what you meant to link to, again - "MSDB Performance Tuning"?

<http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tuning.aspx>

There is plenty to think about, there, anyway.

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Transaction Log Backup Failing as Deadlock Victim Mark D Powell <Mark.Powell2@hp.com> - 2014-01-28 12:58 -0800
  Re: Transaction Log Backup Failing as Deadlock Victim Erland Sommarskog <esquel@sommarskog.se> - 2014-01-28 22:55 +0100
    Re: Transaction Log Backup Failing as Deadlock Victim rja.carnegie@gmail.com - 2014-01-28 16:58 -0800
      Re: Transaction Log Backup Failing as Deadlock Victim Erland Sommarskog <esquel@sommarskog.se> - 2014-01-29 08:34 +0000
        Re: Transaction Log Backup Failing as Deadlock Victim Mark D Powell <Mark.Powell2@hp.com> - 2014-01-30 12:34 -0800
          Re: Transaction Log Backup Failing as Deadlock Victim Mark D Powell <Mark.Powell2@hp.com> - 2014-01-30 13:07 -0800

csiph-web