The easiest method would be to place your case statements in a derived table and then perform a grouping of the results.

select year, max(yada)...

from

( yourqueryhere

) myDerivedTable

GROUP BY year

I would look at the emailTable populating process.

1 - create a distinct list of users who should receive email

2 - populate table information by level of validity

create table #tEmailList

insert into...

I guess I need an alibi for my alias...

I did NOT know that the locking behavior on temp stopped at 6.5...

thx...

determine where the query is slowing down.. Review the execution plan.

this site is GOLD! http://www.simple-talk.com/sql/performance/execution-plan-basics/

SWAGs

1.. place a clustered index on RevID in the temporary...

The sub-query is required by the bizlogic

If one of transaction is between 01/09/2008 to 30/09/2008 then it will show all related transaction.

if exists(SELECT material_code

FROM MATERIAL_UPDATES

GROUP BY material_code

HAVING count(*) > 1)

BEGIN

select "Table has Duplicates"

RETURN

END

else

select "No Duplicates"

-- your query here

I have used the Insert Into with Exec (below) and recently ran into a Sql issue. Insert Into with Exec() does not allow nested uses.

create table #tYada (...)

Insert...

As far as I know, when a function is returning a table the input cannot change in the query.

Every different row in the above table join would return...

That worked to a 'T'.

thanks!

Daryl

SqlProfiler could be the means to determine how the data is being inserted into your table.

Especially if you have a test environment to weed out the normal course...

First thing would be determining where your data is originating. Your query starts with Part when it appears it should start at invoice. (by the right join)

<determine a...

Do you have the new query? thanks

If the parameters are not used for the recursion (and I don't think they are) you can just create the view w/0 the where statement. Then when you access...

Syntax below works for commonTableExpressions

create vYourViewHere

as

with cteName as

(...)

select * from cteName

Note: cte's are usable in sprocs the point to remember is to add the semicolon before the WITH

create proc...

If you are fortunate enough to have a Data Layer this change may be less painful.

1- update sprocs with addition criteria 'group' (defaults to All, or not filtering)

2- at the...