Re: after servererror trigger question

epipko_at_gmail.com wrote:
> Again, it makes sense.
> How do one be proactive and be alerted when user, suddenly, can't
> connect to prod d/b?

As has been said, you cannot do this on the database side of things. That leaves the client side. You'd have to write some sort of app which attempts to connect to the database from the client side and if it can't, send a notification (email, page, etc) to the DBA. But are you sure you really want to do this? Any network burp will cause the DBA to be notified. There are other reasons a client would not be able to access the db (most of them network related) that are not really the responsibility of the DBA to fix.

And in my shop, if a user can't connect to the database, I hear about it soon enough!

Cheers,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown