Take a look at the database sizes, if it has a lot unallocated shrink it. If the log file is huge take a backup.

No dice on the updating of stats, It still takes about the same amount of time. 5-6mins.

I'm going to start logging from a few system views and see...

Server 2003 or 2008?

That's a good call, I'll give that a try and let you know.

they ran for about 10mins and I shut them...

I didnt have any luck with these queries.

Ya it still took about 6mins. There is the plan.

Jeff Moden (6/28/2010)

Now THAT's interesting... although an INDEX SEEK is listed, no predicates...

ya i thought of that about 8mins ago, the query is still running.

lmu92 (6/28/2010)

Jeff Moden (6/28/2010)

Except for the fact that I'm generally against using INT to store ISO dates, there's no need to change it here because it won't help for this...

done.

The other index on it is clustered,

CREATE UNIQUE CLUSTERED INDEX [Idx_BALEOD20091SkuStoreEOD] ON [dbo].[BALEOD2009]

(

[EODDate] ASC,

[Store] ASC,

[SkuNumber] ASC

)WITH...

Here is the...

EODDate is an int atm, I am working on some tests to see if changing it will help but the date is used as an int thoughout the database. ...

There is no gain with using Count(*), yup everything is running on an index