Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2002-08-31 : 15:18:08
|
| I've read the sqlteam articles on SQL email with interest. The single largest limiting factor on SQL email I can see is the 100 or 200 character limit imposed on the address field doesn't lend to a single request being sent to more than 2 or 3 addresses.I've got to implement a group email for an online training web which will be used to remind users to take the course. The database usually contains from 10,000 to 50,000 users. I imagine the worst case is at the start of the course, this group facility will be used to 'remind' everyone that it's time to take the course.I've implemented ASP and ASP.NET email before, but have no experience with SQL email. I'd appreciate any feedback on the benefits of looking into achieving this 'group email' within SQL as opposed to implementing it within ASP.Some concerns I have about ASP/ASP.NET - efficency - unsure how many names can be included in a to/cc/bcc, but I'm under the impression that 50 or so simultaneous addresses can be passed to CDONTS in a single ASP call. - choking - Any feedback on whether SMTP servers can handle 50,000 email requests with 1 to address each? - Is it necessary to pace the delivery of email to an smtp server? What's a reasonable rate? Is the workload of a request with 5 to addresses identical to the workload of 5 email requests with 1 to address?Thanks in advance for any comments.SamC |
|
|
Onamuji
Aged Yak Warrior
504 Posts |
Posted - 2002-08-31 : 20:24:00
|
| best bet would to be to have an email_queue table and a flag that says if the message has been sent or not ... you then would write a procedure to interact with a dll that sends email ... this is the best method I have found and used without problems for over 2 years now... |
 |
|
|
|
|
|
email performance - SQL vs ASP.NET