Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-04-15 : 08:42:50
|
| Chiefley writes "My IT department is balking at installing Outlook in a production system where I intend to use DTS packages to automate some ETL processes. I know CDO could be used for messages from within packages, but one of my main goals is to get an email from the SQL Server Agent when the job fails. Do I have an alternative to having a MAPI client like Outlook invoked and running in the SQL Server Agent account? It does seem kind of hokey and insecure if that is the way MS expects it to work? What can I tell my IT department to quell their security fears?I am sorry that its not a very interesting question. Thanks in advance.Regards,Chiefley" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-04-15 : 08:52:53
|
quote:
Do I have an alternative to having a MAPI client like Outlook invoked and running in the SQL Server Agent account? It does seem kind of hokey and insecure if that is the way MS expects it to work? What can I tell my IT department to quell their security fears?
It may not allay their fears exactly, but I would think if MICROSOFT uses this setup for their own SQL Servers, it's probably OK for the rest of us.  As far as security, that basically rests on the profile used by SQL Mail, and would best be controlled through Exchange. I'm not really fluent with what Exchange can do, but I imagine that an account can be configured to only send email, and reject all incoming email, if so desired. Certainly a rule can be created on that account to delete all incoming mail, or restrict incoming mail to specific users/accounts. If the profile is linked to a domain account, then the domain administrators can further audit and enforce security on that account. |
 |
|
|
|
|
|
Sql Server Agent and Outlook