As I said, the problem is in your data definitions. Please post them if you still want any help.

Here is a link that explains how to get the best...

It's still CHARINDEX, you just have to be more persistent:

Select CharIndex( @string, '_', CharIndex(@string, '_') + 1)

This returns the second occurrence of "_" in @string.

Well, it parses just fine for me in SQL2005, so it must be in your data definitions.

Nice job, Jack. This could serve as a textbook example of how to provide technical support.

As it happens, I was just working with a customer today on CLR assemblies, and it seems that the key/login is supposed to be used to "Sign" the assembly when...

I agree, it's confusing. I am not sure what the answer is either.

Hmm, good point. I am not really sure why then. Maybe it just always does that after an IF EXISTS statement because it has to do that for...

I believe that you have to make the login the Owner (or executor?) of the Assembly

There is also this view which was included in the daily emailer just last month:

/*

vwTableInfo - Table Information View

This view display space and storage information for every table in...

Exactly the same as NOT IN for this case in SQL 2005. In general that is what I usually see for SQL 2005.

OK, I just checked it myself. It's because the step before just CREATE-d the table. DML statements in the same batch will not be able to see it...

Show us the whole script. It's probably because of something that happens the step before or the step after.

Interestingly, on SQL 2005, the first query is marginally faster.

SYSJOBHISTORY is only written to on completions: step completion and Job completion. To get current status you will have to start in SYSJOBACTIVITY.

LEFT(std_acc, 9)

But why are you adding characters onto a 9 character field if you only want it to be 9 characters?

And why are you using a cursor for this?