maybe they didn't performance test on a full size data cut?

does the stored procedure have parameters? Maybe its using an innapropriate (cached) execution plan for specific parameters. e.g. wider date range?

How about using a bigger sample when gathering statistics?

compare the execution plans between the 1 day and 10 day executions. You may have to use a hint, or an explicit temporary table.

How up to date are your statistics?...

Once you have created the partition function and scheme, you should just be able to drop any clustered index and rebuild specifiying the partition scheme

Microsoft investigating

Thanks iwg

I kind of came to the same conclusion in the conversation I was having with myself above!!

Its good to have it confirmed though!

Andy

Thanks Ed

I have a feeling that as we are clustered, tempdb will need to go on the SAN

Ah, as this is a cluster, does this mean that all my datafiles need to go on the SAN?

Thanks SQLBill. All our other clusters are configured with Tempdb on the SAN. I was concerned about making full use of that 300Gb.

Andy

It didn't!

Hoping that:

http://support.microsoft.com/?id=923849

will solve the problem!

Andy

Ric

MS have confirmed that it is a bug with SQL 2005. If you have a support agreement, you should raise a call. We are currently in the process of getting...

OK, when I dropped the publication when connected to the server, rather than from my PC, it came up with the same error, but allowed me to continue and the publication...

Thanks Noel

I'm looking at partitioning to help maintain some very big tables, (i.e. rebuild indexes at partition level rather than table level). As long as queries perform the same with...

This is a stored procedure with 2 parameters. If I run the SQL with the parameters hard coded (i.e. not as a stored procedure call), I get a different (better)...