quote:

---

FYI - Here's the modified script to get this to work with CDONTS (which is free).

Create Procedure sp_SMTPMail
	@SenderName varchar(100),
	@SenderAddress varchar(100),
	@RecipientName varchar(100),
	@RecipientAddress varchar(100),
	@Subject varchar(200),
	@Body varchar(8000)
AS	
	SET nocount on
	
	declare @oMail int --Object reference
	declare @resultcode int
	
	EXEC @resultcode = sp_OACreate 'CDONTS.NewMail', @oMail OUT
	
	if @resultcode = 0
	BEGIN
		EXEC @resultcode = sp_OASetProperty @oMail, 'From', @SenderAddress
		EXEC @resultcode = sp_OASetProperty @oMail, 'To', @RecipientAddress
		EXEC @resultcode = sp_OASetProperty @oMail, 'Subject', @Subject
		EXEC @resultcode = sp_OASetProperty @oMail, 'Body', @Body
	
		EXEC @resultcode = sp_OAMethod @oMail, 'Send', NULL
	
		EXEC sp_OADestroy @oMail
	END
	

	SET nocount off
GO

To test, call with something like:

exec sp_SMTPMail @SenderName='You', @SenderAddress='YourName@YourMailSite.com',
@RecipientName = 'YouAgain', @RecipientAddress = 'YourName@YourMailSite.com',
@Subject='SQL Mail Test', 
@body='This is a test message from SQL Server.  Smile! It worked.'

The only catch is getting CDONTS installed on your SQL Server without dumping excess junk there. I found one of our SQL Servers had IIS installed on it by mistake, and CDONTS came with it.

Should this (and Merkin's Original) go into the Script Library Forum?

------------------------------------------------------------------
Contractor$ never die, they just leave for higher-paying project$.

Edited by - AjarnMark on 07/26/2001 19:43:49

---

quote:

---

Lin, you're going to have to find some space for your database. This impacts EVERYTHING you have running. SQL needs space to shuffle things around. If you don't have it, you're in deep (word I won't use on the site)

Mike
"A program is a device used to convert data into error messages."

---

quote:

---

OK Lin

The way I see it, you have 2 options.

One is create a job that would send you an email. Then create an alert that fires when you run out of space, and calls that job. Go have a look around the "Alerts" in enterprise manager to see what I mean.

The other way, and I think this is better...run a script every night that will check to see if anything is getting too big, then send an email if it is.

nr wrote a script to do this and posted it here,

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6891&FORUM_ID=6&CAT_ID=3&Topic_Title=To+check+Database+File+Growth&Forum_Title=Administration

all you would have to do is change the email code to use sp_SMTPMail instead of xp_sendmail.

Good luck!




Damian

---

quote:

---

EXEC xp_sendSMTP 'SMTP.server', 'from', 'to', 'subject', 'body'

can i know what is smtp server what should i put in ???

now i am using windows 2000 server, it comes together with smtp service, is smtp services same with smtp server, or i need to install another smtp server ?????

---