How far back ya wanna go on the Month-x columns?

Heh... yeah... I remember that discussion... It's a bloody shame that Microsoft keeps changing features to bugs especially on things like this... no wonder lot's of folks are hesitant to...

Well... hats off to MS... ALL of our servers had the MS patch and all switched time correctly at the appointed time.  Even my home machine updated correctly and on...

Peter,

Ol' friend, thanks for the feedback.  I haven't been "blessed" with 2k5 yet, so I always wonder how these things work out there.

Yes, you're correct.  Randy originally said that this...

Randy and Ken,

Yeah, it's pretty much an addiction to me.   Thanks for the feedback... it's part of the addiction

Peter, not sure what your's would do if you added a primary key to the table but it currently take about 15 seconds to do 4,000 rows, 60 seconds to...

As some have suggested, both methods get pretty slow, even in the presence of proper indexing, simply because of the triangular joins involved. As is typical of large triangular joins,...

Yep... I have to agree... single table would be the way to go... makes for "common code" which makes life simple and you don't have to use dynamic SQL or...

I think that once you read my "long" post with the sample code, you'll find that 10 reps on a single job will be the way to go...

As some have suggested, step 1 would be to ensure the Recovery Mode on TempDB is set to SIMPLE.

Step 2 would be to rewrite your code so it doesn't use...

Oki-doki... change of plans... decided to go full-bore on this one (Man! This one was FUN! ).  First, if you had SQL...

I was doing some checks on your formulas... because of the integer math you are using everywhere, you're coming up with the Statistical Median when you have an even number...

The "Pivot option" you speak of is not available in SQL Server 2000... and this IS an SQL Server 7/2000 forum.

I would solve each of the 4 separately... the ol' "peel one potatoe at a time" usually works the best on these types of things but, of course, that's your...

Richard,

Michael is correct... the most efficient way is to simply make sure that GETDATE() is used in the procs that update the table.  As you point out, that does not...