dready
asked on
Setting up SQL Mail without Outlook
Does anyone know what is the best (and preferably easiest (-:) way to setup SQL Mail without having to install Outlook on the Database Server and leaving it open? I want to be able to create an operator that will receive mails when jobs fail, etc. But i hate to have Outlook installed and running on the server.
So: What are my alternatives? And which advantages/disadvantages do they have? And do you have links to a place where I can find info on how to set it up?
The server is running windows 2003 server enterprise edition and SQL Server 2000 SP4. We do have an exchange server (but on another machine).
Thanks,
dready
So: What are my alternatives? And which advantages/disadvantages do they have? And do you have links to a place where I can find info on how to set it up?
The server is running windows 2003 server enterprise edition and SQL Server 2000 SP4. We do have an exchange server (but on another machine).
Thanks,
dready
Keith
You don't need Outlook for SQL to send email to the Exchange Server, just set up SQL mail and it works.
Hi, In SQL2000, you HAVE to have a mapi client (eg Outlook) to use the SQL Mail Feature. This I am afraid is the easiest way.
In SQL2005 however you dont need to install Outlook, so if you feel very strong that you dont want to install outlook on a production machine, then u have to opt for buying a sql 2005 licenses.
In SQL2005 however you dont need to install Outlook, so if you feel very strong that you dont want to install outlook on a production machine, then u have to opt for buying a sql 2005 licenses.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes I agree, It has to be installed to get the required Dlls registered. And also to have a user account setup on Outlook that would be used by SQL Server. And yes it doesnt have to be running all the time. just installed.
I personally dont see any risks to 'installing' Outlook on a production machine either. The risk would be when your SQL Server Mail Account that is suppose to send mail starts to receive mails and some one opens it from that computer. Check with ur Exchange Administrator whether you can limit the SQL Server Mail User to just send mails and not reciev mails. (might be helpful if it can do that) And lock the password somewhere safe so normal users dont have access to it.
I personally dont see any risks to 'installing' Outlook on a production machine either. The risk would be when your SQL Server Mail Account that is suppose to send mail starts to receive mails and some one opens it from that computer. Check with ur Exchange Administrator whether you can limit the SQL Server Mail User to just send mails and not reciev mails. (might be helpful if it can do that) And lock the password somewhere safe so normal users dont have access to it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot. THe links wizilling provided are very usefull!
On our current server, we have outlook installed, but for some reason xp_sendMail only sends the mails when outlook is open. I hope i'll be able to avoid that on the new server.
On our current server, we have outlook installed, but for some reason xp_sendMail only sends the mails when outlook is open. I hope i'll be able to avoid that on the new server.