How about:

select a.vndid, a.vndname, a.invdate, a.invamt, b.invamt

from #test a inner join #test b

on a.vndname = b.vndname and

a.invdate = b.invdate and

(a.invamt - b.invamt) between 5.0 and 30.0

How about:

declare @date as datetime

declare @dw as varchar(6)

set @date = '09-01-2010'

set @dw = cast(datepart(dw,@date) as varchar(1))

select @dw

select daysoff, @dw

from #TempDaysOff

where daysoff like '%' + @dw + '%'

That's why I suggested setting concat_null_yields_null to false. It will prevent the concatenation of nulls from resulting in a null string. Safer to do it your way, since...

Shouldn't the coalesce be around the column, not the variable?

declare @Notes VarChar(Max)

Select @Notes = @Notes + COALESCE(Note + ',' ,'')

From DesignRequestsHistory Where DesignRequestNumber = 540

select @Notes

Also you may have...

If you don't have the .mdf file for the database, and there's no available backup and the file recovery tools can't bring it back, then there is no way to...

Is it possible to drop the view, perform the update, then re-create the view?

Another stab..

Indexed views on the table?

OK, reduced to stabbing in the dark. Are there computed columns in the table? You indicated the DDL was abbreviated, otherwise, I wouldn't ask...

Thanks for the interesting problem,...

Those old values should be money data types, right? So they should have 4 decimals. The values you've listed don't have any. Did you just drop them...

The error message only makes sense if some process is trying to put a numeric data type into a character typed column. The raw update doesn't do that. ...

Let's see the DDL for the table, including any triggers that might be firing. The error message says you're trying to convert a numeric to a character. That...

The only really big reason I have found to put the BLOBs in the database is that it makes synchronizing a whole lot easier. If the metadata and the...

Thank you so much for your insights.

I totally agree with everything you guys have said so far.

I think they wanted to have an architecture where any object (or table) can...

So the user at the front end has to scroll, potentially, through a list of 60,000 entries to pick the two he's looking for? Isn't there any way to...

So why pull back all 60K rows?

select distinct rep_lname from [tHeirarchyData] where Period = @P_lookup

will get you just a list of rep last names from the period you...