X-Received: by 10.182.111.227 with SMTP id il3mr6380254obb.41.1391116053428; Thu, 30 Jan 2014 13:07:33 -0800 (PST)
X-Received: by 10.182.119.133 with SMTP id ku5mr125317obb.4.1391116053242; Thu, 30 Jan 2014 13:07:33 -0800 (PST)
Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!uq10no7155908igb.0!news-out.google.com!vg8ni1igb.0!nntp.google.com!c10no7149034igq.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.databases.ms-sqlserver
Date: Thu, 30 Jan 2014 13:07:33 -0800 (PST)
In-Reply-To: <8af3ac60-ef8f-4f84-95bc-16f8645cd3b5@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=15.219.153.74; posting-account=qJFqbQkAAACYQSLN0-cvP6ydkRfuOu6u
NNTP-Posting-Host: 15.219.153.74
References: <a226b43d-9e59-4686-b21c-b818fed76ef8@googlegroups.com> <XnsA2C3E928BBD6BYazorman@127.0.0.1> <06522420-91a7-4905-8d4b-9d397a3eed68@googlegroups.com> <XnsA2C46177C41FDYazorman@127.0.0.1> <8af3ac60-ef8f-4f84-95bc-16f8645cd3b5@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d6dc7b6c-6513-494c-9ca2-d3620451ea00@googlegroups.com>
Subject: Re: Transaction Log Backup Failing as Deadlock Victim
From: Mark D Powell <Mark.Powell2@hp.com>
Injection-Date: Thu, 30 Jan 2014 21:07:33 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: csiph.com comp.databases.ms-sqlserver:1657

On Thursday, January 30, 2014 3:34:40 PM UTC-5, Mark D Powell wrote:
> On Wednesday, January 29, 2014 3:34:53 AM UTC-5, Erland Sommarskog wrote:
> 
> > (rja.carnegie@gmail.com) writes: 
> 
> > 
> 
> > > Is this what you meant to link to, again - "MSDB Performance Tuning"? 
> 
> > 
> 
> > > 
> 
> > 
> 
> > ><http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tun
> 
> > 
> 
> > >ing.aspx> 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > There is plenty to think about, there, anyway. 
> 
> > 
> 
> > 
> 
> > 
> 
> > Yes, thanks for adding the link, when I forgot to paste it into my post. 
> 
> > 
> 
> > 
> 
> > 
> 
> > -- 
> 
> > 
> 
> > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
> 
> 
> Thanks to both of you.  I have opened the article and will give the indexes a shot.  Fortunately I do have a backup history purge which is the second step in my daily error log switch job.
> 
> 
> -- Mark --

If would appear that SQL Server 2008 R2 RTM comes with some of the recommended indexes already defined:

/****** Object:  Index [PK__restoreh__FDC4B0311C873BEC]    Script Date: 01/30/2014 16:00:11 ******/
ALTER TABLE [dbo].[restorehistory] ADD PRIMARY KEY CLUSTERED 
(
	[restore_history_id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
GO


/****** Object:  Index [restorehistorybackupset]    Script Date: 01/30/2014 16:00:35 ******/
CREATE NONCLUSTERED INDEX [restorehistorybackupset] ON [dbo].[restorehistory] 
(
	[backup_set_id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
GO

I have not checked all the tables yet. -- Mark --