Much better... but won't work in SQL Server 2000 which is what this forum is...

Heh... or just pay attention to what you're doing   Either way, a trip to the estimated execution plan probably would have shown the...

Glad it helped...

Any chance of you posting your final code?

Your solution can not work without the numbers table... at least a link would have been nice...

Steal from the "sp_" code...

Sure... when you first create a server instance, they are not there.  They only appear when something first needs them... then, they persist.

Um... be careful in that assumption... while this works...

DECLARE @SomeDate DATETIME

SET @SomeDate = '05.24.2007'

PRINT @SomeDate

...this will not...

DECLARE @SomeDate DATETIME

SET @SomeDate = '24.05.2007'

PRINT @SomeDate

...because the implicit format is understood to be mm.dd.yyyy.

Still worth it... maybe someone else can get a leg up on things if they manage to find it...

"Error like this object already exists?"  What on Earth are you doing with the Dynamic SQL?

What... and miss out on all that high-class entertainment?

Duplicate records DO happen on staging tables used for preprocessing rows from third parties, especially telephone companies... Either a "UNIQUE WITH IGNORE DUPES" index must be used (comparitively very slow)...

Heh... you're right... wrong article... it was about "RAAS", not "RAC"...

You'r still nothing more than a spammer...  I can't understand why you don't get your product evaluated on this site......

This should do it nicely... classic cross-tab... you might be able to use SQL Server 2005 PIVOT as well... either way, it'll solve your slowdown because each row is only...

Now... that's a bummer...