September 26, 2008 at 10:28 am
Hi,
Our sysadmins are moving our database-mail (and Outlook-profile accounts) over to a new Exchange server.
Do we need to restart our SQL-server instances (and/or SQL Agent services) after the move?
What else do we need to do as a result of this change?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
September 26, 2008 at 11:13 am
I don't think so, but you might need a restart of dbmail. Haven't tested this in 2005 and no Exchange server (or 2) to try with.
September 26, 2008 at 11:16 am
Is there a stop/start in 2005 as there was in 2000? Don't see one, and I think that each time you call the XP, it logs on, doesn't keep a session open like MAPI.
September 26, 2008 at 11:21 am
Steve Jones - Editor (9/26/2008)
Is there a stop/start in 2005 as there was in 2000? Don't see one, and I think that each time you call the XP, it logs on, doesn't keep a session open like MAPI.
We are trying it now for a couple of accounts. Will post further once I know more.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
September 26, 2008 at 11:59 am
We tried the move for mail accounts on servers using both OUTLOOK (sql mail) and SMTP (db mail) to send mail.
For SQL Server 2005 instances using smtp (db mail): All I had to change was the server name in the db mail configuration screens, with no service restart necessary
However, I get the following error when using xp_sendmail on SQL 2000 instances - after changing the name of the Exchange server in OUTLOOK:
Msg 18025, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80004005
Running "xp_stopmail", "xp_startmail" fixed that.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply