Defining Alert for System Errors

Hi,
I want to define alert for system error messages but it seems that we cannot
alter these messages like SQL Server 2000 to be logged in Windows events.
For example error #208, is it possible?
Thanks in advance,
LeilaNo, we cannot change whether system errors are written to eventlog or not in 2005, I'm afraid. I
guess you have to look for some external utility which monitors the eventlog. The good news is that
the messages in EventLog now has the same Event number as the SQL Server error number (which makes
it easier to write code that reads the eventlog and acts on certain errors).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Leila" <Leilas@.hotpop.com> wrote in message news:Ov$2kalOHHA.1248@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I want to define alert for system error messages but it seems that we cannot alter these messages
> like SQL Server 2000 to be logged in Windows events. For example error #208, is it possible?
> Thanks in advance,
> Leila
>|||Whay if an application is upgraded from SQL Server 2000 to 2005! The
backward compatibility is missed!? It was very easy to define this alert in
previous version..
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eEExMvlOHHA.4244@.TK2MSFTNGP04.phx.gbl...
> No, we cannot change whether system errors are written to eventlog or not
> in 2005, I'm afraid. I guess you have to look for some external utility
> which monitors the eventlog. The good news is that the messages in
> EventLog now has the same Event number as the SQL Server error number
> (which makes it easier to write code that reads the eventlog and acts on
> certain errors).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:Ov$2kalOHHA.1248@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> I want to define alert for system error messages but it seems that we
>> cannot alter these messages like SQL Server 2000 to be logged in Windows
>> events. For example error #208, is it possible?
>> Thanks in advance,
>> Leila
>|||I didn't check what happens with the "always log to eventlog" for system error on an upgraded SQL
Server, but most probably, this setting will not be upgraded (since the system part of sys.messages
isn't really a table anymore), so that will be lost.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Leila" <Leilas@.hotpop.com> wrote in message news:ee5LeBmOHHA.324@.TK2MSFTNGP06.phx.gbl...
> Whay if an application is upgraded from SQL Server 2000 to 2005! The backward compatibility is
> missed!? It was very easy to define this alert in previous version..
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eEExMvlOHHA.4244@.TK2MSFTNGP04.phx.gbl...
>> No, we cannot change whether system errors are written to eventlog or not in 2005, I'm afraid. I
>> guess you have to look for some external utility which monitors the eventlog. The good news is
>> that the messages in EventLog now has the same Event number as the SQL Server error number (which
>> makes it easier to write code that reads the eventlog and acts on certain errors).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Leila" <Leilas@.hotpop.com> wrote in message news:Ov$2kalOHHA.1248@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> I want to define alert for system error messages but it seems that we cannot alter these
>> messages like SQL Server 2000 to be logged in Windows events. For example error #208, is it
>> possible?
>> Thanks in advance,
>> Leila
>>
>