I'm sure they're looking for an answer on this one, but my answer would be "None of the above"...

1. All of the updates will cause some improper change...

Good documentation and examples of the problem, Ryan!

Matt Marston (5/13/2008)

---

The PIVOT statement can be useful at times, but it is handy to know that anything that can be done with a PIVOT statement can be converted to...

benjamin.nelson06 (5/13/2008)

---

Very interesting as I have been working on doing a similar thing now for a few days. However I needed a Grand Total Column and a Grand Total...

srienstr (5/13/2008)

---

From my read of the code, it appeared to be storing (or intended to store) multiple time frames,...

quortex (5/13/2008)

---

Firstly with my previously pasted in code which looked at the TOP entry and added the new amount I would like to try this with OPTION(MAXDOP 1). However I...

srienstr (5/13/2008)

---

Danielle:

Don't bother with the loop at all, substitute in a join.

----Segment Level Supply

INSERT INTO @ConversionTesting(Quarter, Source, Segment, Metric,Value)

select Q.Quarter, 'Converted' as Source, MarketsegmenttypeCode, 'Inventory', sum(NumUnits)

from dbo.tbl_BldgSegments bs

...

Thanks, Hawkeye. I appreciate the feedback.

developmentalmadness (5/13/2008)

---

Splitting a string may be trivial in T-SQL but that doesn't mean it's the best tool for the job. The CLR is vastly faster for splitting strings the longer...

Danielle...

Hard to tell because...

Absolutely correct about the cross-join... change the 11,000 to 1,000,000 and see how fast it works.

Thanks, David... real good to see that you're still around, too! 🙂

You'll also find a lot of folks that suggest not using them because Microsoft could change them at any time... Heck, they do that with documented features :hehe:

Heh... I never use the first release of anything... not even from Peter 😛

Just DATEADD the two columns together and then do the simple math.