I think I was able to solve the problem. This is how I think it works (correct me if I'm wrong):

When I start a job logged in as myself, the...

Bits from BOL:

SETUSER is included in Microsoft SQL Server 2005 for backward compatibility only. SETUSER may not be supported in a future release of SQL Server. We recommend that...

Bits from BOL:

SETUSER is included in Microsoft SQL Server 2005 for backward compatibility only. SETUSER may not be supported in a future release of SQL Server. We recommend that...

Got it -- sorry 🙁

I didn't know that posting on different forums is not allowed -- just wasn't sure what forum to post to. It seems like a security/access rights issue, but it may...

It would -- as long as there is no performance hit while retrieving data from a table that has a computed column that is not persisted and not indexed.

Thanks, Piotr -- I learned something new, even though it's not applicable in this case 🙂

Thanks for the info, GSquared 🙂

Computed columns (persisted or indexed) definitely have merit, but it looks like they are not going to help me in this case 🙁

Well, MS decided to keep this function in SQL 2008, so they probably have some vested interest in it. Since I can't use it to create a persisted computed column,...

Ok, tried this:

create table tblA (pk int not null primary key identity(1,1), col1 varbinary(8), col2 as convert(varchar(18),replace(upper(sys.fn_varbintohexstr(col1)),'X','x')) persisted)

and got this:

Msg 211, Level 23, State 107, Line 1

Possible schema corruption....

Ah, persisted computed column -- I've never used it! That may be just what I need. Do you know if there is a performance impact while running queries that retrieve...

There is a varbinary(8) column in TableA, and there is an external system that can't digest it, so I created an extra column (varchar(18)) to contain the hex representation of...

Ok, in lieu of replies I just replaced my "for insert" trigger with "instead of insert" one. The latter doesn't contain update statements and thus doesn't fire the update trigger....

Yes, so the sequence is as this:

1. insert into TableA executed

2. insert trigger fires

3. insert trigger updates Column1 in TableA (update TableA executed)

4. update trigger fires in response to step...

I had no problems sending emails from a 64-bit SQL 2005 using Database Mail. I had to make the profile I was using Public and Default though (it didn't require...