Successful Backup Messages No More...

re: Successful Backup Messages No More...

Tom Moreau — Mon, 29 Oct 2007 17:30:02 GMT

Is this flag officially documented or is it an undocumented-use-at-your-own-risk type of thing?

re: Successful Backup Messages No More...

Andrew Kelly — Mon, 29 Oct 2007 17:31:28 GMT

I am told it will be documented in Katmai. That's a good thing ey:)

re: Successful Backup Messages No More...

Linchi Shea — Tue, 30 Oct 2007 14:04:18 GMT

It should have been the other way around in the first place. In other words, if someone wants to see that informative message, he should do somethig to turn it on. For me, I'm perfectly fine with the no-news-is-good-news approach as the default.

re: Successful Backup Messages No More...

AaronBertrand — Tue, 30 Oct 2007 14:32:02 GMT

Andrew, I have received positive feedback on Connect #266957 (actually just last week). See:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=266957

re: Successful Backup Messages No More...

Kevin3NF — Tue, 30 Oct 2007 16:45:24 GMT

Thanks Andrew....we manage several hundred SQL instances, many of which have hundreds of databases. You can imagine the size and uselessness of the associated errorlogs, eh?

Good option to present to our customer base.

Kevin3NF

re: Successful Backup Messages No More...

kfarlee — Tue, 30 Oct 2007 20:15:11 GMT

Linchi,

If I was designing it now, that's how I'd do it. Unfortunately as far as we can determine, that message has been there since Sybase days.

By now, there are hundreds of scripts that are depending on that message for some obscure management function, and I'd hear the screams from here if I took it out. So, this is the next best thing.

Expect this to make it into more regular syntax a'la Aaron's Connect item when I can get it in. Likely Katmai +1.

re: Successful Backup Messages No More...

Mark Hedtke — Tue, 27 Nov 2007 19:54:44 GMT

Very enlightening post for those who barely have time to come up for air. There is usually alot we miss when software turnover prevents us from digging deeper to find tidbits like this. One of the keys to making any code work is education. At the public education institution level, a great deal of the vital information like this never sees the day of light. In fact many institutions are still offering SQL Server 2000 and still testing for certification, although public support for it by Microsoft literally ends on Feb 2008. Certainly is great to be certified on dated material just in case a few hundred thousand sites are still using it.

re: Successful Backup Messages No More...

Michael Abair — Thu, 27 Dec 2007 19:11:55 GMT

This has saved me big as I have thousands of databases (500 per instance) getting 23 log backups and 1 full backup per day! What a headache. One thing to note for others in my shoes if you use database maintenance plans to run your backups remember that those traces are connection specific. You can get around that by adding the trace flag to the sql server services startup parameters (this makes the trace global). Heres a link detailing how

http://www.sqlservercentral.com/Forums/Topic421160-357-1.aspx?Update=1

'Backup Completed' is NOT an Error Message

Kevin Kline — Thu, 17 May 2012 14:48:58 GMT

I recommend that you set your SQL Server to use the startup traceflag DBCC TRACEON (3226) to disable backup success message...

re: Successful Backup Messages No More...

SCP — Mon, 21 Jan 2013 18:51:28 GMT

Hi Andrew,

How would you get rid of messages from the secondary server? trace 3226 does not help:

Here is the reference question but no one has answered it yet.

http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/99686208-65ae-47c5-b928-be74b0d21321/

Please let me know if you happen to know any solution for this.

Thanks,

SCP

re: Successful Backup Messages No More...

Andrew Kelly — Tue, 22 Jan 2013 21:43:04 GMT

I don't know of any way to rid the log of the restore messages you are concerned with. I see why one would want to supress them just like the backups but so far I haven't found a trace flag for that. If I do find one I will post here.