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 |
|
demonbane
Starting Member
10 Posts |
Posted - 2003-11-05 : 11:52:18
|
| Hello Everyone,I got a strange problem with my sql mail that I am hoping someone can help me with.I have a program called PeopleSoft that uses a third party software called Sqr. An sqr is basically sql code just formatted differntly. This one large sqr I have calls on xp_sendmail to send a preformated email to users when a certain instance occures. Well enough background I think.The process works well and it sends the emails as required. The problem I am having is that my networking people are complaining mightly that I am causing the exchange server to come to a crawl and or corrupting the message stores. They state that the exchange server resources are being peaked constantly. At this point they are pushing for me to stop using sql mail at all. OK, here is my question. Since sql mail basically uses outlook (mapi client) to send the email it should be no different than me sending out hundreds of emails. It is a client of the exchange server after all. I do not see a logical reason why the exchange server should be behaving this way when my sql server sends out messages.My last question. If I am using a storeproc that will call xp_sendmail do I have to use xp_startmail before I call xp_sendmail and then do I have to call xp_stopmail afterward? Does it matter? It seems to work fine just calling xp_sendmail. I'm just consern that it may not be closing it's connection to the exchange server and is repeating itself multiple times thus creating and maintain multiple connections to the exchange server.Once again thanks for the help. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-11-05 : 12:09:26
|
| Not sure why this would happen, but to answer your last question, SQL won't open multiple Exchange sessions.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-05 : 12:26:57
|
| No, you do not need to run xp_startmail before and then xp_stopmail after. How do the server admins know that the sqrs are causing the problem? I would doubt that they know what is causing the problem, they are just pointing the finger right now. Have they even run any diagnostic tools to see where the problem is?Tara |
 |
|
|
demonbane
Starting Member
10 Posts |
Posted - 2003-11-05 : 13:26:47
|
| As far as I know they are not running any diagnostics to prove that it is sql mail. It just seems to be a coincidence that what ever store that the sql mail profile is on has a problem. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-05 : 13:29:28
|
| I would be very surprised if SQL Mail is causing the problem on Exchange. Are you running service pack 3 or 3a for SQL Server 2000? If not, you might consider installing 3a in case the service pack fixes this type of problem, if it is in fact caused by SQL Mail.Tara |
 |
|
|
demonbane
Starting Member
10 Posts |
Posted - 2003-11-05 : 13:50:10
|
| This is currently what I have.Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft CorporationEnterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)product version 8.00.760product levelSP3 EditionEnterprise Edition |
 |
|
|
|
|
|