check http://www.riverland.net.au/text/look_first/netcode.html

it has a litle list and also has some smily explanation.

There also exists a sp_cycle_errorlog.

Downside of this is that it apears not to be working when used in a sqlagent job.

(complaints abount not being sa, even if I make sa...

correct, noeld.

if you have e.g. hp-openview monitoring software, you could have your last step raise an error (user defined errormessage / alert) to the windows eventlog, and hp-openview could pick it...

AFAIK there is no feedback to the job launched by sqlagent and it will only document that the job is started by the alert-related jobschedule. Based on this, I guess...

script it from the old db and run the script on the new db, removing the script-references to the old db.

- did you perform checkdisk ?

- does the server report memory-bank-problems ? (eventvwr/system)

how about this :

select e.deptno, e.ename, e.job, M.MaxSal

from emp e

inner join

(select deptno, max(sal) as MaxSal from emp group by deptno) M

on e.deptno = M.deptno

Keep it simple and stupid.

Follow Jonathan's guidelines.

check the ISDATE function in BOL

It probably got into your db as result of a restore or attach from an SQL7 db.

I've noticed the same with a "convert(int(5),floatcol)"- SQL7-statement.

There 's al mass of info regarding this subject on the net.

I prefer surrogate keys because they make it mandatory for the db-user to understand the datamodel, so e.g. symantic...

works fine over here. I'd go for Allen_Cui's option.

Check your windows-eventlog and look for other (e.g. windows) lisence messages.

They might be related to your issue.

did you stop/start sqlagent ? (is needed when you activate the first alert)