|
|
Posted by Erland Sommarskog on 09/20/05 00:21
[Posted and mailed]
"Mike" <mjorlando@campsystems.com> writes:
>I agree, sp_update_alert is not the answer. I actually checked the
>sysalerts table and only found 10 rows in this table. None matched the
>message which I'm trying to suppress. Since I'm looking for a
>message_id, I also tried calling sp_altermessage 17055, 'WITH_LOG',
>'false' using the event ID 17055 found in the Windows Event Viewer and
>also tried with 18265, which is the first part of the event
>description, but no luck. Any other suggestions? Thanks.
I spoke too soon when I said that it is not possible.
You can use trace flag 3226 to suppress these messages.
There is also a related trace flag 3001 that suppresses logging
to msdb.backuphistory.
These flags are undocumented with all that means. On the other hand,
I got them from a Microsoft engineer who said it was OK to share them.
--
Erland Sommarskog, Stockholm, esquel@sommarskog.se
Navigation:
[Reply to this message]
|