July 26, 2012 at 1:39 pm
Hi, I have a SQL 2005 server, call it OldProd, and a new production SQL 2008, call it NewProd. I have Database Mail enabled on both servers. OldProd has an existing profile and account we use to send email alerts. NewProd is being set up as the new production SQL Server so I'm trying to configure database mail to mirror OldProd's db mail profile and account.
However, for some reason any new profile or account being created in Database Mail on NewProd is seen only on OldProd, never on NewProd. In other words, NewProd profiles and accounts are stored in OldProd's msdb database, not NewProd's! In fact, if I create a new profile with the same name as the one on OldProd, it gives me a 'profile already exists' message, even though it doesn't exist on NewProd.
It looks like NewProd is pointing to OldProd's Database Mail rather than its own.
How does this happen and how do I make NewProd save its own new profiles and accounts locally, rather than OldProd?
Thanks for any suggestions and advice.
July 27, 2012 at 6:20 am
No one has the answer to this dilemma?
July 27, 2012 at 9:08 am
How are you creating your profiles and accounts, using the GUI or scripts?
If you are using scripts can you post them please?
Cheers
Chris
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply