> I don't know if just starting an light dll to send an e-mail will be a
> heavy process (I was thinking in local mail, or a local relay mail
> server, a remote server could be more problematic, mainly if the link
> could be down).
>
> If it will be using in a "select" I will agree 100% with you, but just
> on some inserts, I think this could not be so problematic.
>
> select
> Invoice.Number, Invoice.CustomerID,
> Mail_UDF(Customer.Email, 'I select your invoice !', Customer.Name ||
> cast(Invoice.Total as varchar(20)))
> from
> Invoice join
> Customer on (Customer.CustomerID = Invoice.CustomerID)
>
> will be really a stupid decision.... ;-)
>
> But I think the "event" approach will be better, or even another
> application that keeps pooling the server for new mails to be delivered
> as you suggested.
>
> >Alan

If your UDF is craeating the text of the email and dropping the file into
the drop directory, then you can get carried away with the size of the email
content. If, as you say, it's making an SMTP connection to do the work then
that's a bad idea (as you say).
The select example is right out (as monty python would say).
I have a mailer application which fires via AT (not even a standalone
service to avoid yet more server overhead) and it does more than just mail.
You are likely wo want it to update records according to when an email was
sent etc etc. So I don't need events either.
Alan