Maybe I'm missing something... but I don't see where that script generates that output.

The problem with displaying that data on one line is your Y/N on Ind3. You need...

GROUP 1!

The base idea here is to boil this query down to its base elements and figure out everything that's causing issues. At this point, you'd start commenting out joins...

I can't see how that code would give you that error. This works fine:

DECLARE @b-2 nvarchar(50)

SET @b-2 = 'afeakfe;a-086'

SELECT CASE WHEN CAST(RIGHT(@b,3) as varchar(3)) =...

I knew something didn't look right with that STR function this whole time. I kept looking at it and ignoring it, then looking at it and ignoring it. ...

Ok, starting all the way at square 1. This *should* run.

If it does run, begin by uncommenting (removing the --'s) from the where criteria one line at a time....

Ok, continuing to try to isolate the error... try this one:

SELECT TOP 100

CASE

WHEN orig.orig_system is...

After running mine?

Now that I'm getting used to it (and occasionally begrudgingly adding my from clause before my select) it's working a little better. It's still pretty sluggish and occasionally annoying...

Please refer to the article in my signature for the proper way to post table DDL and sample data. Doing so will get you better, quicker answers.

When I read (and then later fully comprehended) the way...

Have you ever actually talked to a Group 1?...

Does this run? (I converted your query to use current JOIN syntax... hopefully I didn't mess it up. If I did, replace the FROM and WHERE with your...

Greg Snidow (11/3/2008)

Seth, I was rolling laughing at that. I'm a huge Dilbert fan, so any time I see 'Gah', it elicits strong images of Dilbert...

Trying... to... resist...

Gah.

Jeff Moden explains this technique in his article located here:

http://www.sqlservercentral.com/articles/Advanced+Querying/61716/

If you don't read that article, make note of several things.

1. I added a clustered index...