I also caught the missing comma and answered "syntax error" 

The "usual suspect" here is permissions.  Try logging into your box and into EM as your SQL Server Agent and see what happens when you execute the Tasks manually.

And even if the question stated that you started in the Master database, as you propose, a syntax would only be raised if you *haven't*, for some reason, put an...

It's not that difficult in QA, and you'll learn more by typing it out:

ALTER TABLE roles

ADD CONSTRAINT MyConstraintName

UNIQUE (UserID, GroupID)

This will force the combination of the two columns to be...

I don't know whether this matters to you at all or not, but to me, using a UDF for this seems counter-intuitive.

UDFs should take an input value, do something to...

...now that's what I mean by being careful.  

Ok, but I can't imagine any reason why you could SELECT, but not UPDATE these records.

You should be able to take:

SELECT ...

FROM ...

WHERE ...

and turn it into

UPDATE ...

FROM ...

WHERE...

If you gotta do a loop, you might as well do it in ASP.  Doing it in a SPROC may or may not be faster, but probably not by much.

I'm...

You should be able to do one multi-row UPDATE, since you want to modify all the child records of a certain record...just construct the WHERE clause accordingly.

UPDATE <table>

SET whatever='whatever',...n

WHERE ParentID='ParentID'

I...

Be careful using CONCAT_NULL_YEILDS_NULL, especially since you'll be stringing together a bunch of these substrings, presumably to concatenate them all together into an XML doc.  (see where I'm going with...

Another possibility might be (all depends on your specific data) converting the EDI docs to XML and importing it that way.

Just a thought.

Ummm, your original post said you didn't want to have to use the TABLE name as a constant. 

I can't imagine why using the trigger name inside the trigger would...

Look up sysobjects in BOL. 

The parent_obj  column contains the parent table of triggers.

You might want to check your transaction log size settings in the database properties.  The hosting company only allows you 17 megs of space, but is the database set up...

Maybe this isn't as cool as CHECKSUM(), but couldn't you also do some sort of outer join and test for nulls?