HA!

And I thought you meant Quality Face Time...

Oh jeez. The internet has let me down... again...

:alien:

I had to go and look QFT up. :ermm:

See, even when you're not teaching, you're teaching. There's a darn good reason you're an MVP.

Yeah, all the training, access to Microsoft programmers, PSS, the vendors, the swag, Steve's magnificent night of gambling... All great stuff.

The absolute most important part of the Summit is getting...

Then that doesn't sound like a structural problem. It must be one of logic.

There's no way for innacurate numbers to be entered or values to be changed over time?

How far is it off? Hundreds & thousands or only a few dollars or cents? If it's the smaller number, it could be rounding errors. You didn't specify the data...

Frequently you'll see people refer to meeting at PASS or going to PASS. Then they're not talking about the Professional Association of SQL Server users, as linked above, but the...

There isn't a replacement. From the BOL:

ALL

This option is deprecated and maintained only for backward compatibility. It does not grant all possible permissions. Granting ALL is equivalent to granting the...

It does parse, but try generating an estimated execution plan. It fails immediately. Parse and compile aren't the same.

I've done this two different ways.

First was to add an effective date column and then always sort by effective date to get the latest effective value.

Better was to create...

I agree with Gail. Further, it seems like a SurveyId would be a great candidate for the leading edge of the clustered index on most tables. This would store the...

No, it's pretty clear. Here's the first statement that jumps out:

And then,...

WOO HOO!

Another well deserved reward. That's terrific. Congratulations Gail. Holy cow, all the cool kids seem to be hanging out here now.

You're going to be at PASS?

You've got a beverage-of-your-choice coming from me. Track me down.

No way in the world to even suggest a solution without at least the execution plan.

Great. If you did need to pursue the CASE statements, you can't use "= LIKE." So you'd have to change

AND lc.locstring =

to

AND lc.locstring LIKE