Great news. The clustered index physically orders the data on disk. Updating one table from another probably does a Join and Joining on data from two tables where the data...

Yep - Estimated execution  plan is a great tool.

I know you have a drop dead of Monday but I wold consider killing the job and putting a CLUSTERED INDEX on...

Hi Ben - hope you are OK! Does the execution plan look OK, Is it using indexes on the dunns number?

Hi Ralf - I think SQL service packs are cumulative so sp4 should include sp 1..3

I get mine here http://support.microsoft.com/kb/290211/EN-US/

Allen

Sorry - I was not clear.

This problem did occur under XP and was fixed by AS sp1. So perhaps AS sp1 would fix the problem under yuor W2k installation.

You could use a stored proc

CREATE PROCEDURE rpDeptSalesValue @StartWeek INT, @EndWeek INT

AS

SELECT

   Sales.SalDept

   Sum(SalesValue)

FROM

   Sales

WHERE

    SalWeekNo Between @StartWeek AND @EndWeek

GROP BY Sales.SalDept

I see you are runningWin 2000 but I understand that for XP this problem was solved in Analysis Services sp1.

Oops - thanks Giles - I missed that.

Yep - different collations just cause pain. I try to have a standard base SQL build here but even so sometimes you need different...

Hi Ben,

I think your first UPDATE looked better from a set based approach. The second one has too many sub selects for me.

I would probably look at ...

1. Indexes and...

I think you have two options.

Change the collation on the tables so that the collation is the same using ALTER TABLE. The easiest way here is to generate ALTER TABLE...

I think you need to wrap square brackets around your invalid column names.

Not sure if this is the cause but CRLF is x0D0A Char(13) + Char(10)

Agree with above regarding memory. MS advised me not to use Boost Fibers and not to limit processor usage, Windows 2003 and SQL work closely enough not to require too...