Heh... Wasn't going to say anything about that so it wouldn't change anything but, I absolutely agree, that's normally a prime give-away.  Another dead give-away is the level of urgency even if...

I'll be the first to agree with making the end result pretty... I'm just not sure why they don't do that at the presentation layer... or, maybe that's the problem? ...

Heh... nice job Serqiy... guess I didn't have enough coffee   I didn't think of the crosstab-like solution.  Very cool.

Hmmm... I'm using SQL Server 2000 sp4 Developer's Edition and it works fine...

Heh... THAT would be funny, indeed.  Thanks, Antares...

My pleasure, Maqy... thank you and James for the feedback.

You don't need to archive as an "Excel" file... just export it as a Tab delimited file and reimport if you need it.

If you don't have SA privs, BCP would...

Simple, elegant, and nasty fast, James.  Well done...

If you use BCP along with the "Simple" Recovery Mode on a staging table with no indexes and no triggers, the load of 150,000 rows should take no more than...

Thanks for the feed back James and Nickie...

Oh yeah... absolutely.  That's part of why I was asking... Not having a PK on the table really seems dumb.  And, I absolutely agree with Marty on this one... the...

That's what I'm talking about   Once we know what you need, Jan, lots of folks have great solutions to avoid the cursor. ...

You've missed the point, entirely, and I doubt you have any real understanding of the solution.  Good luck, "sir"... you will need it.

Considering that only two rows of a table are being accessed for the original question being asked, I'd have to say the delta-t would be measured in nano-seconds.  The big...

LOL!  This is where I'm supposed to say something like "Do it in the app"...