Yes, with Case, i.e. (the query of course depends on how to stick taba and tabb together):

SELECT

TabA....

CASE

WHEN TabA.code='A' THEN TabB.DataA

...

I would say that if the functionality is sufficient, then use the charindex.

If you do:

DECLARE @sum FLOAT, @s-2 VARCHAR(255)

SELECT @s-2 = 'foobar', @sum = 0.0

WHILE...

Btw - the new execution plans are here:

http://mdgrosse.net/perf-hash.plan.txt

and

http://mdgrosse.net/perf-hash.sqlplan

Ok - heres the biggie:

When I change all "LEFT JOIN" in "LEFT HASH JOIN" (only in my query, I don't touch the views) the whole query needs under one second...

No, this table has only one record (accounting stuff: the client and the current year).

If it is not relevant in which order the phone numbers (home, ...) is preferred, left join this:

...

LEFT JOIN (

SELECT

customerid,

MAX(phonenumber)...

http://mdgrosse.net/perf.plan.txt

or

http://mdgrosse.net/perf.sqlplan

thx

Michael