At first glance, I would say that your performance issues are probably related to the using a loop in the first place, which results in records being updated one by...

My apologies for resurrecting such an old post, but I am looking for a similar solution as Gary's question, and have not found any answers yet.

In response to Daniel's suggestion...

Remember that COALESCE will find the first non-NULL value, therefore it will evaluate to true if any one of the values in the list is valid. Look at your other...

I have not tried this myself, but offhand I would say you could try using a subreport, or data region (tablix within a tablix).

Look at the following article about using CTEs to concatenate field values, to see if this might resolve your problem:

http://www.codeproject.com/KB/reporting-services/Concatenate_Field_Values.aspx

Usually, in such a case, you might be better served with a stored procedure, using dynamic SQL.

If you want to keep your query in the report, however, you can do...

Could you not rather do your categories as one parameter, with a drop-down list?

Then your query becomes a simple WHERE Category IN (@Category)

Not exactly what I had in mind...

Is there a date column in your t_facility_valuation table, and would it contain yesterday and today's dates?

Sorry, I was making assumptions, and we all know where that leads...

In my example t1 and t2 are aliases to the same table, but the principle can be adapted to...

You could try something like this:

SELECT

T1.sm as ID,

CAST(t1.last_modified) AS DATE) as Curreny_Reporting_Period,

SUM(t1.amount) AS Current_Reporting_amount,

CAST(t2.last_modified AS DATE) as Previous_Reporting_Period,

SUM(t2.amount) AS Previous_Reporting_amount,

SUM(t1.amount) - ISNULL(SUM(t2.amount),0) as Amount_Difference

FROM t1

LEFT OUTER JOIN t2

ON t1.nr =...

I would say you need some sort of employment history table,

with the following details:

Department_Identifier, Employee_Identifier, Start_Date, End_Date

I assume that you need help formulating the WHERE clause of your query to allow for NULL conditions?

There are several ways to accomplish this, the best being to write your...

One possibility would be to use 2 queries - one for types 04 and 05 only, and one for everything else - joined with a UNION ALL.

When using the LIKE comparison, SQL will not use any index on the column being queried, causing performance to suffer.

Where possible, use a more specific operator, or try using BETWEEN...