Failed to notify 'DBA' via email

We have some SQL jobs those run on a schedule basis. These jobs are setup to
notify us via email in case of job fails. However, Some time we get this
error "Failed to notify 'DBA' via email." Initially I thought it may be b/c
of mail server was not available but our exchnage server admin has looked at
exchange logs and not found any thing at that time. I also looked at the SQL
server logs and did not find any issues. My question is: is there any thing
can go wrong in the SQL server that can cause this probelm?
Help is appreciated.
Thanks,
MohMoh,
FWIW - SQL Server MAPI will only wait a certain amount of time to deliver a
message. If it cannot get out, then the mail will 'fail' even though
Exchange is up and running and healthy. It might be Exchange, networking,
domain issues, etc. that cause the problem.
If you Google on "sql mail Failed to notify" you will see a few comments on
this, without any real help that I could find.
(Unless xp_smtp_sendmail would work for you.)
RLF
"Moh Abb" <mabbas@.aligntech.com> wrote in message
news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> We have some SQL jobs those run on a schedule basis. These jobs are setup
to
> notify us via email in case of job fails. However, Some time we get this
> error "Failed to notify 'DBA' via email." Initially I thought it may be
b/c
> of mail server was not available but our exchnage server admin has looked
at
> exchange logs and not found any thing at that time. I also looked at the
SQL
> server logs and did not find any issues. My question is: is there any
thing
> can go wrong in the SQL server that can cause this probelm?
> Help is appreciated.
> Thanks,
> Moh
>|||"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:ePA64pj3EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Moh,
> FWIW - SQL Server MAPI will only wait a certain amount of time to deliver
a
> message. If it cannot get out, then the mail will 'fail' even though
> Exchange is up and running and healthy. It might be Exchange, networking,
> domain issues, etc. that cause the problem.
> If you Google on "sql mail Failed to notify" you will see a few comments
on
> this, without any real help that I could find.
Generally I find if you don't absolutely need to use Exchange, setup a local
SMTP server right on teh SQL box and send email through that directly.
Eliminates timeouts, etc.
> (Unless xp_smtp_sendmail would work for you.)
> RLF
> "Moh Abb" <mabbas@.aligntech.com> wrote in message
> news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> > We have some SQL jobs those run on a schedule basis. These jobs are
setup
> to
> > notify us via email in case of job fails. However, Some time we get this
> > error "Failed to notify 'DBA' via email." Initially I thought it may be
> b/c
> > of mail server was not available but our exchnage server admin has
looked
> at
> > exchange logs and not found any thing at that time. I also looked at the
> SQL
> > server logs and did not find any issues. My question is: is there any
> thing
> > can go wrong in the SQL server that can cause this probelm?
> >
> > Help is appreciated.
> >
> > Thanks,
> > Moh
> >
> >
>
>

Failed SAS70 Audit

Our company recently got a bad mark on our SAS70 audit because I act as both DBA and developer.

Audit firm went so far to say DBA shouldn't have access to production data! Anybody else experience this?

Is there a way to log ALL sa transactions for review and audit? If so, that may satisfy them.

Thanks!

Scott

So nobody has experienced a SAS70 auditor claiming a developer cannot act as DBA?Or that the DBA cannot have rights to the production data?

|||I know that there are 3rd party products for auditing. We often allow application developers and database analysts (stored proc/ETL writers) access to production data. We have gone through two SAS70 audits without issues related to this.

Generally speaking, these people are not assigned to the sysadmin role of the server.

Michelle

Failed SAS70 Audit

Our company recently got a bad mark on our SAS70 audit because I act as both DBA and developer.

Audit firm went so far to say DBA shouldn't have access to production data! Anybody else experience this?

Is there a way to log ALL sa transactions for review and audit? If so, that may satisfy them.

Thanks!

Scott

So nobody has experienced a SAS70 auditor claiming a developer cannot act as DBA?Or that the DBA cannot have rights to the production data?

|||I know that there are 3rd party products for auditing. We often allow application developers and database analysts (stored proc/ETL writers) access to production data. We have gone through two SAS70 audits without issues related to this.

Generally speaking, these people are not assigned to the sysadmin role of the server.

Michelle
sql