I hope it didn't seem like I was arguing that there wasn't an implicit conversion going on. The error...

:unsure:I'm not trying to be difficult, and I know not seeing the CTE setion would give a more complete picture, but I just can't post it....a) it's very long and...

Jason - I hear you. But even if there was some implicit type conversion problems with the omitted CTE section, I don't see how it would explain why the...

I'm not sure if I can. Let me see if I can duplicate this problem with a simple example that doesn't disclose anything my company might get antsy about...

Ah, just found this MSKB 181362. But it sounds like you are on top of it based on your results....you actually switched context.

mchofman (3/30/2010)

---

...but I still receive an error...

Marco - Wow...that all sounds impressive. Unfortunately, I have no idea what you are talking about...:blush:. I'm really just an old-school programmer that tries to put on a...

If the job owner has sysadmin authority, the job always runs under the SQL Agent security context.

...

If the job step Run As is blank, the step runs under the job...

liteswitch (3/29/2010)

---

Yes indeed, this is why when I create jobs I usually set the owner to be the SQL Agent account, as otherwise if you've a job assigned to a...

My understanding is that in order to use Windows Authentication between two server, you'll need to setup some sort of "trust" between the servers and use the impersonate check box...

I don't think so...at least that's not what I'm seeing. Apparently...

Thanks Bhuvnesh. But that's soft of like answering, "Yes" to a three part question. 😉 I'm trying to figure out HOW to control the security context of...

Thanks for the response HappyCat59, I'm familiar with proxy accounts but I think you are misunderstanding my problem. The problem is not the security within the execution context of...

Never mind...customer had some outdated code with mistakes in it. The problem code was simply putting values into @coll (lower case "L") instead of @col1 (number "1")...looks almost identical...

I solved a similar problem using a table-valued function that took two dates, used a while loop that iterates through the dates using DATEADD(...), and loaded each new date into...

Never mind, found the info I needed here:

http://www.databasejournal.com/features/mssql/article.php/3302341/SQL-Server-and-Collation.htm

So changing the code above to this, fixed it:

DECLARE @C VARCHAR(10)

,@i VARCHAR(10)

SET @i=192

SET...