Different SQL mail

my config is SQL2000, outlook xp
now i use xp_sendmail to see email from SQL2k
how can i use different mail profiles for different database?
or i can control it at script level?
i have searched google for this and seems it is feasible.
grateful if you could give me some hints.
by the way, i am going to upgrade SQL2000 to SQL2005.
Thanks a lot.
tonyHi
xp_startmail will take a different MAPI profile. You may want to use XPSMTP
instead where the source can be specified http://www.sqldev.net/xp/xpsmtp.htm
John
"Tony WONG" wrote:
> my config is SQL2000, outlook xp
> now i use xp_sendmail to see email from SQL2k
> how can i use different mail profiles for different database?
> or i can control it at script level?
> i have searched google for this and seems it is feasible.
> grateful if you could give me some hints.
> by the way, i am going to upgrade SQL2000 to SQL2005.
> Thanks a lot.
> tony
>
>

Different SQL mail

my config is SQL2000, outlook xp
now i use xp_sendmail to see email from SQL2k
how can i use different mail profiles for different database?
or i can control it at script level?
i have searched google for this and seems it is feasible.
grateful if you could give me some hints.
by the way, i am going to upgrade SQL2000 to SQL2005.
Thanks a lot.
tonyIf you upgrade to 2005, consider using Database Mail instead. See sp_send_dbmail in the 2005
documentation.
As for 2000, I believe that you optionally can use different profiles, although I've never tried it.
See the documentation for xp_startmail.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tony WONG" <x34@.hknet.com> wrote in message news:enyZScRwGHA.1272@.TK2MSFTNGP05.phx.gbl...
> my config is SQL2000, outlook xp
> now i use xp_sendmail to see email from SQL2k
> how can i use different mail profiles for different database?
> or i can control it at script level?
> i have searched google for this and seems it is feasible.
> grateful if you could give me some hints.
> by the way, i am going to upgrade SQL2000 to SQL2005.
> Thanks a lot.
> tony
>

Different SQL mail

my config is SQL2000, outlook xp
now i use xp_sendmail to see email from SQL2k
how can i use different mail profiles for different database?
or i can control it at script level?
i have searched google for this and seems it is feasible.
grateful if you could give me some hints.
by the way, i am going to upgrade SQL2000 to SQL2005.
Thanks a lot.
tonyHi
xp_startmail will take a different MAPI profile. You may want to use XPSMTP
instead where the source can be specified [url]http://www.sqldev.net/xp/xpsmtp.htm[/url
]
John
"Tony WONG" wrote:

> my config is SQL2000, outlook xp
> now i use xp_sendmail to see email from SQL2k
> how can i use different mail profiles for different database?
> or i can control it at script level?
> i have searched google for this and seems it is feasible.
> grateful if you could give me some hints.
> by the way, i am going to upgrade SQL2000 to SQL2005.
> Thanks a lot.
> tony
>
>

differences in SSIS file locations in SQL Server Agent step

When adding an SSIS step to a SQL Server Agent job, when selecting the location of a config file, the dialog lets you select from the database server you're working with. If selecting the location of the package itself (when the source is File System), the dialog lets you select from the machine where Management Studio is sitting instead of from the database server. Is that intentional? And if so, why? Should I just use a fully qualified file name for the package location rather than one using a drive letter?
Hmmm... Yeah, I don't like that. Though I always deploy by storing the packages in SQL Server versus the file system.

Let's let some of the other guys chime in.... I do know that some of the folks around here never use the SSIS step type in Agent and instead use the Command Line type. That allows them to build the DTEXEC statement the way they need it to be.|||

Phil Brammer wrote:

I do know that some of the folks around here never use the SSIS step type in Agent and instead use the Command Line type. That allows them to build the DTEXEC statement the way they need it to be.

That's might be the way I go. In production we'll be using Control-M anyway, so I might as well just have the command-line all prepped and ready to go for that.
|||

Phil Brammer wrote:

Let's let some of the other guys chime in.... I do know that some of the folks around here never use the SSIS step type in Agent and instead use the Command Line type. That allows them to build the DTEXEC statement the way they need it to be.

And it lets us get the full output of DTEXEC, which is handy for troubleshooting.