i downloaded an rdbms s/w from http://www.vaman.net/vmndataserver.htm
these people claimed that this particular s/w has integrated data server, mail server & web server in2 one.
also they claim that they have a data migration tool which can migrate data from any db to vaman & vice versa.
i tried this data migration tool, & to my amazement , its working just fine.
but somehow, i didn't understand their first claim of having an integrated data server, web server & mail server in2 1. i mean what's the use 4 that?
on the top of it, there enterprise manager is a true copy of MS SQL Server. is it allowed?
isn't there anyone who can stop this?
this is sheer copying of a software.
it is like a copying the source code of a web site & building a new web site by giving a few cosmetic changes.
can u please explain it 2 me.Don't worry dude they have a data migration tool and according to you it is working just fine..... good for you ... why r u concerned about their claims...... if for academic reasons or for knowledge sake u wish to know y they are offering mail, data and web server all in one ...then the reason behind that may be that since nobody such a product ... they may be promoting it as their USP.... probably they cannot compete in the database market with the likes of IBM, Microsoft and oracle without offering a bundle of a product..... the buyer need not go for a separate web or mail server that is what they must be saying...... mean while if their software is working properly take full advantage of it without worrying.
Originally posted by manishbafna80
i downloaded an rdbms s/w from http://www.vaman.net/vmndataserver.htm
these people claimed that this particular s/w has integrated data server, mail server & web server in2 one.
also they claim that they have a data migration tool which can migrate data from any db to vaman & vice versa.
i tried this data migration tool, & to my amazement , its working just fine.
but somehow, i didn't understand their first claim of having an integrated data server, web server & mail server in2 1. i mean what's the use 4 that?
on the top of it, there enterprise manager is a true copy of MS SQL Server. is it allowed?
isn't there anyone who can stop this?
this is sheer copying of a software.
it is like a copying the source code of a web site & building a new web site by giving a few cosmetic changes.
can u please explain it 2 me.
Showing posts with label mail. Show all posts
Showing posts with label mail. Show all posts
Thursday, March 22, 2012
Monday, March 19, 2012
Can the Job Notifications be configured to use a different transport mechanism?
(SQL Server 2000, SP3a)
Hello all!
In our Production environment, we're moving towards a configuration that will preclude the
use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require SQL
Mail, which would leave Net Send as our only available transport.
Is there any way to integrate an additional Notification transport into SQL Server?
Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
make the Notifications leverage something outside the default transports.
Thanks!
John PetersonFor xp_smtp_sendmail, you can just add another step that
sends the email. So if you wanted to notify on failure, just
add a step to the job that you branch to on failure. This
job step can handle the email. You won't have support for
operators but you can write your own - have a table with
whatever email, rules then query this table to find who
should be notified. You can then pass this value to
xp_smtp_sendmail.
-Sue
On Mon, 3 Nov 2003 14:06:18 -0700, "John Peterson"
<j0hnp@.comcast.net> wrote:
>(SQL Server 2000, SP3a)
>Hello all!
>In our Production environment, we're moving towards a configuration that will preclude the
>use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
>E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require SQL
>Mail, which would leave Net Send as our only available transport.
>Is there any way to integrate an additional Notification transport into SQL Server?
>Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
>make the Notifications leverage something outside the default transports.
>Thanks!
>John Peterson
>|||Thanks, Sue!
I had hoped there was a way to integrate the existing Operator aspect, but introduce a new
transport mechanism. It sounds like it won't be that straightforward. :-(
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:85hdqvse38r38os3ul9b6rsvgi600nlt1v@.4ax.com...
> For xp_smtp_sendmail, you can just add another step that
> sends the email. So if you wanted to notify on failure, just
> add a step to the job that you branch to on failure. This
> job step can handle the email. You won't have support for
> operators but you can write your own - have a table with
> whatever email, rules then query this table to find who
> should be notified. You can then pass this value to
> xp_smtp_sendmail.
> -Sue
> On Mon, 3 Nov 2003 14:06:18 -0700, "John Peterson"
> <j0hnp@.comcast.net> wrote:
> >(SQL Server 2000, SP3a)
> >
> >Hello all!
> >
> >In our Production environment, we're moving towards a configuration that will preclude
the
> >use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
> >E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require
SQL
> >Mail, which would leave Net Send as our only available transport.
> >
> >Is there any way to integrate an additional Notification transport into SQL Server?
> >Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
> >make the Notifications leverage something outside the default transports.
> >
> >Thanks!
> >
> >John Peterson
> >
>|||No, it's a bit more of a PITA than that, but at the same time, it gives you
a lot more control. We use this mechanism and we have customized
subjects/bodies, inclusion lists based on various error levels, etc.
A
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> Thanks, Sue!
> I had hoped there was a way to integrate the existing Operator aspect, but
introduce a new
> transport mechanism. It sounds like it won't be that straightforward.
:-(|||Thanks Aaron (and Sue)!
Out of curiosity, do you know whether the Notifications is making a SQL call to
xp_sendmail? If so, would it be possible to "swap out" the underlying xp_sendmail .DLL
and replace it with a xp_smtp_sendmail "wrapper" with the same name as xp_sendmail?
I doubt that the Notifications is making a SQL call to "do its business", but I thought
I'd check. :-)
Thanks!
John Peterson
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> No, it's a bit more of a PITA than that, but at the same time, it gives you
> a lot more control. We use this mechanism and we have customized
> subjects/bodies, inclusion lists based on various error levels, etc.
> A
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > Thanks, Sue!
> >
> > I had hoped there was a way to integrate the existing Operator aspect, but
> introduce a new
> > transport mechanism. It sounds like it won't be that straightforward.
> :-(
>|||Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
Agent does its own MAPI calls.
I'm writing a utility that does xp_smtp_sendmail calls based on your current
alert configuration. The idea is to configure alerts as desired, and then
schedule my .exe every x minutes. My .exe reads off of the alert config
table and reads the eventlog. Based on when each configured alert was fired
the last time, the exe will xp_smtp_sendmail. The current idea is to use
disabled operators (if you enable them, then Agent will complain that it
can't send email).
I'm finishing up this util this week, then I have to wait for it to go on
the web (which might take a few days to a few weeks - I don't have direct
access to the web). Send me an email if you want to give it a try earlier.
I will put it on www.dbmaint.com, free utilities.
--
Tibor Karaszi
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> Thanks Aaron (and Sue)!
> Out of curiosity, do you know whether the Notifications is making a SQL
call to
> xp_sendmail? If so, would it be possible to "swap out" the underlying
xp_sendmail .DLL
> and replace it with a xp_smtp_sendmail "wrapper" with the same name as
xp_sendmail?
> I doubt that the Notifications is making a SQL call to "do its business",
but I thought
> I'd check. :-)
> Thanks!
> John Peterson
>
> "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > No, it's a bit more of a PITA than that, but at the same time, it gives
you
> > a lot more control. We use this mechanism and we have customized
> > subjects/bodies, inclusion lists based on various error levels, etc.
> >
> > A
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > Thanks, Sue!
> > >
> > > I had hoped there was a way to integrate the existing Operator aspect,
but
> > introduce a new
> > > transport mechanism. It sounds like it won't be that straightforward.
> > :-(
> >
> >
>|||Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If you don't mind an
early beta tester, I'd be delighted to try it out earlier! :-)
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
> Agent does its own MAPI calls.
> I'm writing a utility that does xp_smtp_sendmail calls based on your current
> alert configuration. The idea is to configure alerts as desired, and then
> schedule my .exe every x minutes. My .exe reads off of the alert config
> table and reads the eventlog. Based on when each configured alert was fired
> the last time, the exe will xp_smtp_sendmail. The current idea is to use
> disabled operators (if you enable them, then Agent will complain that it
> can't send email).
> I'm finishing up this util this week, then I have to wait for it to go on
> the web (which might take a few days to a few weeks - I don't have direct
> access to the web). Send me an email if you want to give it a try earlier.
> I will put it on www.dbmaint.com, free utilities.
> --
> Tibor Karaszi
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > Thanks Aaron (and Sue)!
> >
> > Out of curiosity, do you know whether the Notifications is making a SQL
> call to
> > xp_sendmail? If so, would it be possible to "swap out" the underlying
> xp_sendmail .DLL
> > and replace it with a xp_smtp_sendmail "wrapper" with the same name as
> xp_sendmail?
> >
> > I doubt that the Notifications is making a SQL call to "do its business",
> but I thought
> > I'd check. :-)
> >
> > Thanks!
> >
> > John Peterson
> >
> >
> > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > No, it's a bit more of a PITA than that, but at the same time, it gives
> you
> > > a lot more control. We use this mechanism and we have customized
> > > subjects/bodies, inclusion lists based on various error levels, etc.
> > >
> > > A
> > >
> > >
> > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > Thanks, Sue!
> > > >
> > > > I had hoped there was a way to integrate the existing Operator aspect,
> but
> > > introduce a new
> > > > transport mechanism. It sounds like it won't be that straightforward.
> > > :-(
> > >
> > >
> >
> >
>|||Great! Send me an email, John (remove the obvious parts), and I can send you
the bits when I'm done with it.
--
Tibor Karaszi
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If
you don't mind an
> early beta tester, I'd be delighted to try it out earlier! :-)
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
> > Agent does its own MAPI calls.
> > I'm writing a utility that does xp_smtp_sendmail calls based on your
current
> > alert configuration. The idea is to configure alerts as desired, and
then
> > schedule my .exe every x minutes. My .exe reads off of the alert config
> > table and reads the eventlog. Based on when each configured alert was
fired
> > the last time, the exe will xp_smtp_sendmail. The current idea is to use
> > disabled operators (if you enable them, then Agent will complain that it
> > can't send email).
> > I'm finishing up this util this week, then I have to wait for it to go
on
> > the web (which might take a few days to a few weeks - I don't have
direct
> > access to the web). Send me an email if you want to give it a try
earlier.
> > I will put it on www.dbmaint.com, free utilities.
> > --
> > Tibor Karaszi
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > Thanks Aaron (and Sue)!
> > >
> > > Out of curiosity, do you know whether the Notifications is making a
SQL
> > call to
> > > xp_sendmail? If so, would it be possible to "swap out" the underlying
> > xp_sendmail .DLL
> > > and replace it with a xp_smtp_sendmail "wrapper" with the same name as
> > xp_sendmail?
> > >
> > > I doubt that the Notifications is making a SQL call to "do its
business",
> > but I thought
> > > I'd check. :-)
> > >
> > > Thanks!
> > >
> > > John Peterson
> > >
> > >
> > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > No, it's a bit more of a PITA than that, but at the same time, it
gives
> > you
> > > > a lot more control. We use this mechanism and we have customized
> > > > subjects/bodies, inclusion lists based on various error levels, etc.
> > > >
> > > > A
> > > >
> > > >
> > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > Thanks, Sue!
> > > > >
> > > > > I had hoped there was a way to integrate the existing Operator
aspect,
> > but
> > > > introduce a new
> > > > > transport mechanism. It sounds like it won't be that
straightforward.
> > > > :-(
> > > >
> > > >
> > >
> > >
> >
> >
>|||Good thinkin' Tibor.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ZZJpb.36406$dP1.121601@.newsc.telia.net...
> Great! Send me an email, John (remove the obvious parts), and I can send
you
> the bits when I'm done with it.
> --
> Tibor Karaszi
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> > Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If
> you don't mind an
> > early beta tester, I'd be delighted to try it out earlier! :-)
> >
> >
> > "Tibor Karaszi"
> <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> > message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > > Alerts does not call xp_sendmail as it did in 6.5 and earlier.
Nowadays,
> > > Agent does its own MAPI calls.
> > > I'm writing a utility that does xp_smtp_sendmail calls based on your
> current
> > > alert configuration. The idea is to configure alerts as desired, and
> then
> > > schedule my .exe every x minutes. My .exe reads off of the alert
config
> > > table and reads the eventlog. Based on when each configured alert was
> fired
> > > the last time, the exe will xp_smtp_sendmail. The current idea is to
use
> > > disabled operators (if you enable them, then Agent will complain that
it
> > > can't send email).
> > > I'm finishing up this util this week, then I have to wait for it to go
> on
> > > the web (which might take a few days to a few weeks - I don't have
> direct
> > > access to the web). Send me an email if you want to give it a try
> earlier.
> > > I will put it on www.dbmaint.com, free utilities.
> > > --
> > > Tibor Karaszi
> > >
> > >
> > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > Thanks Aaron (and Sue)!
> > > >
> > > > Out of curiosity, do you know whether the Notifications is making a
> SQL
> > > call to
> > > > xp_sendmail? If so, would it be possible to "swap out" the
underlying
> > > xp_sendmail .DLL
> > > > and replace it with a xp_smtp_sendmail "wrapper" with the same name
as
> > > xp_sendmail?
> > > >
> > > > I doubt that the Notifications is making a SQL call to "do its
> business",
> > > but I thought
> > > > I'd check. :-)
> > > >
> > > > Thanks!
> > > >
> > > > John Peterson
> > > >
> > > >
> > > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > > No, it's a bit more of a PITA than that, but at the same time, it
> gives
> > > you
> > > > > a lot more control. We use this mechanism and we have customized
> > > > > subjects/bodies, inclusion lists based on various error levels,
etc.
> > > > >
> > > > > A
> > > > >
> > > > >
> > > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > > Thanks, Sue!
> > > > > >
> > > > > > I had hoped there was a way to integrate the existing Operator
> aspect,
> > > but
> > > > > introduce a new
> > > > > > transport mechanism. It sounds like it won't be that
> straightforward.
> > > > > :-(
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Thanks John. :-)
Perhaps I should say that anyone who like to look at this and expect to
install it to provide some feedback are welcome to drop me an email.
(It'll be a freebie when released, so unless you expect to install and play,
you might as well wait a couple of weeks).
I'll post something here when it is on the web.
--
Tibor Karaszi
"John Sitka" <johnsitka@.REMOVEhotmail.com> wrote in message
news:e3eTqjtoDHA.964@.TK2MSFTNGP10.phx.gbl...
> Good thinkin' Tibor.
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:ZZJpb.36406$dP1.121601@.newsc.telia.net...
> > Great! Send me an email, John (remove the obvious parts), and I can send
> you
> > the bits when I'm done with it.
> >
> > --
> > Tibor Karaszi
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> > > Hello, Tibor! That sounds almost *exactly* what I'd be pining for!
If
> > you don't mind an
> > > early beta tester, I'd be delighted to try it out earlier! :-)
> > >
> > >
> > > "Tibor Karaszi"
> > <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> > > message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > > > Alerts does not call xp_sendmail as it did in 6.5 and earlier.
> Nowadays,
> > > > Agent does its own MAPI calls.
> > > > I'm writing a utility that does xp_smtp_sendmail calls based on your
> > current
> > > > alert configuration. The idea is to configure alerts as desired, and
> > then
> > > > schedule my .exe every x minutes. My .exe reads off of the alert
> config
> > > > table and reads the eventlog. Based on when each configured alert
was
> > fired
> > > > the last time, the exe will xp_smtp_sendmail. The current idea is to
> use
> > > > disabled operators (if you enable them, then Agent will complain
that
> it
> > > > can't send email).
> > > > I'm finishing up this util this week, then I have to wait for it to
go
> > on
> > > > the web (which might take a few days to a few weeks - I don't have
> > direct
> > > > access to the web). Send me an email if you want to give it a try
> > earlier.
> > > > I will put it on www.dbmaint.com, free utilities.
> > > > --
> > > > Tibor Karaszi
> > > >
> > > >
> > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > Thanks Aaron (and Sue)!
> > > > >
> > > > > Out of curiosity, do you know whether the Notifications is making
a
> > SQL
> > > > call to
> > > > > xp_sendmail? If so, would it be possible to "swap out" the
> underlying
> > > > xp_sendmail .DLL
> > > > > and replace it with a xp_smtp_sendmail "wrapper" with the same
name
> as
> > > > xp_sendmail?
> > > > >
> > > > > I doubt that the Notifications is making a SQL call to "do its
> > business",
> > > > but I thought
> > > > > I'd check. :-)
> > > > >
> > > > > Thanks!
> > > > >
> > > > > John Peterson
> > > > >
> > > > >
> > > > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > > > No, it's a bit more of a PITA than that, but at the same time,
it
> > gives
> > > > you
> > > > > > a lot more control. We use this mechanism and we have
customized
> > > > > > subjects/bodies, inclusion lists based on various error levels,
> etc.
> > > > > >
> > > > > > A
> > > > > >
> > > > > >
> > > > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > > > Thanks, Sue!
> > > > > > >
> > > > > > > I had hoped there was a way to integrate the existing Operator
> > aspect,
> > > > but
> > > > > > introduce a new
> > > > > > > transport mechanism. It sounds like it won't be that
> > straightforward.
> > > > > > :-(
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
Hello all!
In our Production environment, we're moving towards a configuration that will preclude the
use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require SQL
Mail, which would leave Net Send as our only available transport.
Is there any way to integrate an additional Notification transport into SQL Server?
Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
make the Notifications leverage something outside the default transports.
Thanks!
John PetersonFor xp_smtp_sendmail, you can just add another step that
sends the email. So if you wanted to notify on failure, just
add a step to the job that you branch to on failure. This
job step can handle the email. You won't have support for
operators but you can write your own - have a table with
whatever email, rules then query this table to find who
should be notified. You can then pass this value to
xp_smtp_sendmail.
-Sue
On Mon, 3 Nov 2003 14:06:18 -0700, "John Peterson"
<j0hnp@.comcast.net> wrote:
>(SQL Server 2000, SP3a)
>Hello all!
>In our Production environment, we're moving towards a configuration that will preclude the
>use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
>E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require SQL
>Mail, which would leave Net Send as our only available transport.
>Is there any way to integrate an additional Notification transport into SQL Server?
>Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
>make the Notifications leverage something outside the default transports.
>Thanks!
>John Peterson
>|||Thanks, Sue!
I had hoped there was a way to integrate the existing Operator aspect, but introduce a new
transport mechanism. It sounds like it won't be that straightforward. :-(
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:85hdqvse38r38os3ul9b6rsvgi600nlt1v@.4ax.com...
> For xp_smtp_sendmail, you can just add another step that
> sends the email. So if you wanted to notify on failure, just
> add a step to the job that you branch to on failure. This
> job step can handle the email. You won't have support for
> operators but you can write your own - have a table with
> whatever email, rules then query this table to find who
> should be notified. You can then pass this value to
> xp_smtp_sendmail.
> -Sue
> On Mon, 3 Nov 2003 14:06:18 -0700, "John Peterson"
> <j0hnp@.comcast.net> wrote:
> >(SQL Server 2000, SP3a)
> >
> >Hello all!
> >
> >In our Production environment, we're moving towards a configuration that will preclude
the
> >use of SQL Mail. As far as we know, Job Notifications have three transport mechanisms:
> >E-Mail, Pager, and Net Send. From what we understand, E-Mail and Pager both require
SQL
> >Mail, which would leave Net Send as our only available transport.
> >
> >Is there any way to integrate an additional Notification transport into SQL Server?
> >Ideally, we'd like to use something like xp_smtp_sendmail. But, we're not sure how to
> >make the Notifications leverage something outside the default transports.
> >
> >Thanks!
> >
> >John Peterson
> >
>|||No, it's a bit more of a PITA than that, but at the same time, it gives you
a lot more control. We use this mechanism and we have customized
subjects/bodies, inclusion lists based on various error levels, etc.
A
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> Thanks, Sue!
> I had hoped there was a way to integrate the existing Operator aspect, but
introduce a new
> transport mechanism. It sounds like it won't be that straightforward.
:-(|||Thanks Aaron (and Sue)!
Out of curiosity, do you know whether the Notifications is making a SQL call to
xp_sendmail? If so, would it be possible to "swap out" the underlying xp_sendmail .DLL
and replace it with a xp_smtp_sendmail "wrapper" with the same name as xp_sendmail?
I doubt that the Notifications is making a SQL call to "do its business", but I thought
I'd check. :-)
Thanks!
John Peterson
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> No, it's a bit more of a PITA than that, but at the same time, it gives you
> a lot more control. We use this mechanism and we have customized
> subjects/bodies, inclusion lists based on various error levels, etc.
> A
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > Thanks, Sue!
> >
> > I had hoped there was a way to integrate the existing Operator aspect, but
> introduce a new
> > transport mechanism. It sounds like it won't be that straightforward.
> :-(
>|||Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
Agent does its own MAPI calls.
I'm writing a utility that does xp_smtp_sendmail calls based on your current
alert configuration. The idea is to configure alerts as desired, and then
schedule my .exe every x minutes. My .exe reads off of the alert config
table and reads the eventlog. Based on when each configured alert was fired
the last time, the exe will xp_smtp_sendmail. The current idea is to use
disabled operators (if you enable them, then Agent will complain that it
can't send email).
I'm finishing up this util this week, then I have to wait for it to go on
the web (which might take a few days to a few weeks - I don't have direct
access to the web). Send me an email if you want to give it a try earlier.
I will put it on www.dbmaint.com, free utilities.
--
Tibor Karaszi
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> Thanks Aaron (and Sue)!
> Out of curiosity, do you know whether the Notifications is making a SQL
call to
> xp_sendmail? If so, would it be possible to "swap out" the underlying
xp_sendmail .DLL
> and replace it with a xp_smtp_sendmail "wrapper" with the same name as
xp_sendmail?
> I doubt that the Notifications is making a SQL call to "do its business",
but I thought
> I'd check. :-)
> Thanks!
> John Peterson
>
> "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > No, it's a bit more of a PITA than that, but at the same time, it gives
you
> > a lot more control. We use this mechanism and we have customized
> > subjects/bodies, inclusion lists based on various error levels, etc.
> >
> > A
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > Thanks, Sue!
> > >
> > > I had hoped there was a way to integrate the existing Operator aspect,
but
> > introduce a new
> > > transport mechanism. It sounds like it won't be that straightforward.
> > :-(
> >
> >
>|||Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If you don't mind an
early beta tester, I'd be delighted to try it out earlier! :-)
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
> Agent does its own MAPI calls.
> I'm writing a utility that does xp_smtp_sendmail calls based on your current
> alert configuration. The idea is to configure alerts as desired, and then
> schedule my .exe every x minutes. My .exe reads off of the alert config
> table and reads the eventlog. Based on when each configured alert was fired
> the last time, the exe will xp_smtp_sendmail. The current idea is to use
> disabled operators (if you enable them, then Agent will complain that it
> can't send email).
> I'm finishing up this util this week, then I have to wait for it to go on
> the web (which might take a few days to a few weeks - I don't have direct
> access to the web). Send me an email if you want to give it a try earlier.
> I will put it on www.dbmaint.com, free utilities.
> --
> Tibor Karaszi
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > Thanks Aaron (and Sue)!
> >
> > Out of curiosity, do you know whether the Notifications is making a SQL
> call to
> > xp_sendmail? If so, would it be possible to "swap out" the underlying
> xp_sendmail .DLL
> > and replace it with a xp_smtp_sendmail "wrapper" with the same name as
> xp_sendmail?
> >
> > I doubt that the Notifications is making a SQL call to "do its business",
> but I thought
> > I'd check. :-)
> >
> > Thanks!
> >
> > John Peterson
> >
> >
> > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > No, it's a bit more of a PITA than that, but at the same time, it gives
> you
> > > a lot more control. We use this mechanism and we have customized
> > > subjects/bodies, inclusion lists based on various error levels, etc.
> > >
> > > A
> > >
> > >
> > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > Thanks, Sue!
> > > >
> > > > I had hoped there was a way to integrate the existing Operator aspect,
> but
> > > introduce a new
> > > > transport mechanism. It sounds like it won't be that straightforward.
> > > :-(
> > >
> > >
> >
> >
>|||Great! Send me an email, John (remove the obvious parts), and I can send you
the bits when I'm done with it.
--
Tibor Karaszi
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If
you don't mind an
> early beta tester, I'd be delighted to try it out earlier! :-)
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > Alerts does not call xp_sendmail as it did in 6.5 and earlier. Nowadays,
> > Agent does its own MAPI calls.
> > I'm writing a utility that does xp_smtp_sendmail calls based on your
current
> > alert configuration. The idea is to configure alerts as desired, and
then
> > schedule my .exe every x minutes. My .exe reads off of the alert config
> > table and reads the eventlog. Based on when each configured alert was
fired
> > the last time, the exe will xp_smtp_sendmail. The current idea is to use
> > disabled operators (if you enable them, then Agent will complain that it
> > can't send email).
> > I'm finishing up this util this week, then I have to wait for it to go
on
> > the web (which might take a few days to a few weeks - I don't have
direct
> > access to the web). Send me an email if you want to give it a try
earlier.
> > I will put it on www.dbmaint.com, free utilities.
> > --
> > Tibor Karaszi
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > Thanks Aaron (and Sue)!
> > >
> > > Out of curiosity, do you know whether the Notifications is making a
SQL
> > call to
> > > xp_sendmail? If so, would it be possible to "swap out" the underlying
> > xp_sendmail .DLL
> > > and replace it with a xp_smtp_sendmail "wrapper" with the same name as
> > xp_sendmail?
> > >
> > > I doubt that the Notifications is making a SQL call to "do its
business",
> > but I thought
> > > I'd check. :-)
> > >
> > > Thanks!
> > >
> > > John Peterson
> > >
> > >
> > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > No, it's a bit more of a PITA than that, but at the same time, it
gives
> > you
> > > > a lot more control. We use this mechanism and we have customized
> > > > subjects/bodies, inclusion lists based on various error levels, etc.
> > > >
> > > > A
> > > >
> > > >
> > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > Thanks, Sue!
> > > > >
> > > > > I had hoped there was a way to integrate the existing Operator
aspect,
> > but
> > > > introduce a new
> > > > > transport mechanism. It sounds like it won't be that
straightforward.
> > > > :-(
> > > >
> > > >
> > >
> > >
> >
> >
>|||Good thinkin' Tibor.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ZZJpb.36406$dP1.121601@.newsc.telia.net...
> Great! Send me an email, John (remove the obvious parts), and I can send
you
> the bits when I'm done with it.
> --
> Tibor Karaszi
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> > Hello, Tibor! That sounds almost *exactly* what I'd be pining for! If
> you don't mind an
> > early beta tester, I'd be delighted to try it out earlier! :-)
> >
> >
> > "Tibor Karaszi"
> <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> > message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > > Alerts does not call xp_sendmail as it did in 6.5 and earlier.
Nowadays,
> > > Agent does its own MAPI calls.
> > > I'm writing a utility that does xp_smtp_sendmail calls based on your
> current
> > > alert configuration. The idea is to configure alerts as desired, and
> then
> > > schedule my .exe every x minutes. My .exe reads off of the alert
config
> > > table and reads the eventlog. Based on when each configured alert was
> fired
> > > the last time, the exe will xp_smtp_sendmail. The current idea is to
use
> > > disabled operators (if you enable them, then Agent will complain that
it
> > > can't send email).
> > > I'm finishing up this util this week, then I have to wait for it to go
> on
> > > the web (which might take a few days to a few weeks - I don't have
> direct
> > > access to the web). Send me an email if you want to give it a try
> earlier.
> > > I will put it on www.dbmaint.com, free utilities.
> > > --
> > > Tibor Karaszi
> > >
> > >
> > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > Thanks Aaron (and Sue)!
> > > >
> > > > Out of curiosity, do you know whether the Notifications is making a
> SQL
> > > call to
> > > > xp_sendmail? If so, would it be possible to "swap out" the
underlying
> > > xp_sendmail .DLL
> > > > and replace it with a xp_smtp_sendmail "wrapper" with the same name
as
> > > xp_sendmail?
> > > >
> > > > I doubt that the Notifications is making a SQL call to "do its
> business",
> > > but I thought
> > > > I'd check. :-)
> > > >
> > > > Thanks!
> > > >
> > > > John Peterson
> > > >
> > > >
> > > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > > No, it's a bit more of a PITA than that, but at the same time, it
> gives
> > > you
> > > > > a lot more control. We use this mechanism and we have customized
> > > > > subjects/bodies, inclusion lists based on various error levels,
etc.
> > > > >
> > > > > A
> > > > >
> > > > >
> > > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > > Thanks, Sue!
> > > > > >
> > > > > > I had hoped there was a way to integrate the existing Operator
> aspect,
> > > but
> > > > > introduce a new
> > > > > > transport mechanism. It sounds like it won't be that
> straightforward.
> > > > > :-(
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Thanks John. :-)
Perhaps I should say that anyone who like to look at this and expect to
install it to provide some feedback are welcome to drop me an email.
(It'll be a freebie when released, so unless you expect to install and play,
you might as well wait a couple of weeks).
I'll post something here when it is on the web.
--
Tibor Karaszi
"John Sitka" <johnsitka@.REMOVEhotmail.com> wrote in message
news:e3eTqjtoDHA.964@.TK2MSFTNGP10.phx.gbl...
> Good thinkin' Tibor.
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:ZZJpb.36406$dP1.121601@.newsc.telia.net...
> > Great! Send me an email, John (remove the obvious parts), and I can send
> you
> > the bits when I'm done with it.
> >
> > --
> > Tibor Karaszi
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:%23PfBOLmoDHA.3320@.tk2msftngp13.phx.gbl...
> > > Hello, Tibor! That sounds almost *exactly* what I'd be pining for!
If
> > you don't mind an
> > > early beta tester, I'd be delighted to try it out earlier! :-)
> > >
> > >
> > > "Tibor Karaszi"
> > <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in
> > > message news:QYApb.36350$dP1.121349@.newsc.telia.net...
> > > > Alerts does not call xp_sendmail as it did in 6.5 and earlier.
> Nowadays,
> > > > Agent does its own MAPI calls.
> > > > I'm writing a utility that does xp_smtp_sendmail calls based on your
> > current
> > > > alert configuration. The idea is to configure alerts as desired, and
> > then
> > > > schedule my .exe every x minutes. My .exe reads off of the alert
> config
> > > > table and reads the eventlog. Based on when each configured alert
was
> > fired
> > > > the last time, the exe will xp_smtp_sendmail. The current idea is to
> use
> > > > disabled operators (if you enable them, then Agent will complain
that
> it
> > > > can't send email).
> > > > I'm finishing up this util this week, then I have to wait for it to
go
> > on
> > > > the web (which might take a few days to a few weeks - I don't have
> > direct
> > > > access to the web). Send me an email if you want to give it a try
> > earlier.
> > > > I will put it on www.dbmaint.com, free utilities.
> > > > --
> > > > Tibor Karaszi
> > > >
> > > >
> > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > news:eqa6mhloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > Thanks Aaron (and Sue)!
> > > > >
> > > > > Out of curiosity, do you know whether the Notifications is making
a
> > SQL
> > > > call to
> > > > > xp_sendmail? If so, would it be possible to "swap out" the
> underlying
> > > > xp_sendmail .DLL
> > > > > and replace it with a xp_smtp_sendmail "wrapper" with the same
name
> as
> > > > xp_sendmail?
> > > > >
> > > > > I doubt that the Notifications is making a SQL call to "do its
> > business",
> > > > but I thought
> > > > > I'd check. :-)
> > > > >
> > > > > Thanks!
> > > > >
> > > > > John Peterson
> > > > >
> > > > >
> > > > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > > > news:uJREwHloDHA.684@.TK2MSFTNGP09.phx.gbl...
> > > > > > No, it's a bit more of a PITA than that, but at the same time,
it
> > gives
> > > > you
> > > > > > a lot more control. We use this mechanism and we have
customized
> > > > > > subjects/bodies, inclusion lists based on various error levels,
> etc.
> > > > > >
> > > > > > A
> > > > > >
> > > > > >
> > > > > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > > > > news:#glZ0DloDHA.3024@.tk2msftngp13.phx.gbl...
> > > > > > > Thanks, Sue!
> > > > > > >
> > > > > > > I had hoped there was a way to integrate the existing Operator
> > aspect,
> > > > but
> > > > > > introduce a new
> > > > > > > transport mechanism. It sounds like it won't be that
> > straightforward.
> > > > > > :-(
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
Sunday, February 12, 2012
Can not send mail with xp_sendmail procedure
Hallo!
Environment:
Windows 2000 domain (2 x win2000 sp4 domain conrollers)
Exchange 5.5 running on winnt4.0 member server
SQL 2000 sp3 running on Windows 2000 member server.
I have SQL server running under domain administrator account (both services)
and Outlook 2000 on the same server profile set with the same account and
Exchange 5.5.
SQL agent is set to use that profile and also SQL mail (under support
services in SQL manager). When I test that profile it works OK. I can send
test mail to the operator and all my alerts can send mail fine.
Problem is, that my new application uses xp_sendmail procedure to send mail,
and it doesn't work. I get this error when running the procedure:
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80070005
I found an article Q293422 that descibes this problem but the solution did
not solve the problem. Besides, this article is about Exchange 2000 mailbox
and I'm using 5.5 mailbox.
I just managed to temporary fix this problem. I created new domain user in
AD and it's mailbox in Exchange 5.5. After seting SQL service, SQL agent
service, mail settings in Enterprise manager and new profile in Outlook to
use that new account, everything was working OK. xp_sandmail was working
too. But the next day same problem repaired. xp_sendmail reported same
errors again.
I suspect there are some security isues with SQL service account, but what?
Why is it working OK for one day and then stops the next?
Any ideas would be appreciated! Thanks.
DanSome links to KB articles and other resources helping with config issues, as
well as alternatives to xp_sendmail: http://www.aspfaq.com/2403
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Dan" <mcseman2002@.hotmail.com> wrote in message
news:OT1exV42DHA.2336@.TK2MSFTNGP09.phx.gbl...
services)
mail,
mailbox
what?
Environment:
Windows 2000 domain (2 x win2000 sp4 domain conrollers)
Exchange 5.5 running on winnt4.0 member server
SQL 2000 sp3 running on Windows 2000 member server.
I have SQL server running under domain administrator account (both services)
and Outlook 2000 on the same server profile set with the same account and
Exchange 5.5.
SQL agent is set to use that profile and also SQL mail (under support
services in SQL manager). When I test that profile it works OK. I can send
test mail to the operator and all my alerts can send mail fine.
Problem is, that my new application uses xp_sendmail procedure to send mail,
and it doesn't work. I get this error when running the procedure:
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80070005
I found an article Q293422 that descibes this problem but the solution did
not solve the problem. Besides, this article is about Exchange 2000 mailbox
and I'm using 5.5 mailbox.
I just managed to temporary fix this problem. I created new domain user in
AD and it's mailbox in Exchange 5.5. After seting SQL service, SQL agent
service, mail settings in Enterprise manager and new profile in Outlook to
use that new account, everything was working OK. xp_sandmail was working
too. But the next day same problem repaired. xp_sendmail reported same
errors again.
I suspect there are some security isues with SQL service account, but what?
Why is it working OK for one day and then stops the next?
Any ideas would be appreciated! Thanks.
DanSome links to KB articles and other resources helping with config issues, as
well as alternatives to xp_sendmail: http://www.aspfaq.com/2403
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Dan" <mcseman2002@.hotmail.com> wrote in message
news:OT1exV42DHA.2336@.TK2MSFTNGP09.phx.gbl...
quote:
> Hallo!
> Environment:
> Windows 2000 domain (2 x win2000 sp4 domain conrollers)
> Exchange 5.5 running on winnt4.0 member server
> SQL 2000 sp3 running on Windows 2000 member server.
> I have SQL server running under domain administrator account (both
services)
quote:
> and Outlook 2000 on the same server profile set with the same account and
> Exchange 5.5.
> SQL agent is set to use that profile and also SQL mail (under support
> services in SQL manager). When I test that profile it works OK. I can send
> test mail to the operator and all my alerts can send mail fine.
> Problem is, that my new application uses xp_sendmail procedure to send
mail,
quote:
> and it doesn't work. I get this error when running the procedure:
> Server: Msg 18025, Level 16, State 1, Line 0
> xp_sendmail: failed with mail error 0x80070005
> I found an article Q293422 that descibes this problem but the solution did
> not solve the problem. Besides, this article is about Exchange 2000
mailbox
quote:
> and I'm using 5.5 mailbox.
> I just managed to temporary fix this problem. I created new domain user in
> AD and it's mailbox in Exchange 5.5. After seting SQL service, SQL agent
> service, mail settings in Enterprise manager and new profile in Outlook to
> use that new account, everything was working OK. xp_sandmail was working
> too. But the next day same problem repaired. xp_sendmail reported same
> errors again.
> I suspect there are some security isues with SQL service account, but
what?
quote:
> Why is it working OK for one day and then stops the next?
> Any ideas would be appreciated! Thanks.
> Dan
>
>
Subscribe to:
Posts (Atom)