Heh... yeah... so they would say! After seeing the cruddy stored procedures they wrote (like sp_SpacedUsed, for example), it must be a "black light" 😛

Jeff Moden (12/28/2007)

---

Koji Matsumura (12/28/2007)

---

Jeff,

with SET STATISTICS IO ON

SELECT TV.Feature, TV.RunStatus, 100.00 * COUNT(*) / B.FeatureCount

:

GROUP BY TV.Feature,...

Koji Matsumura (12/28/2007)

---

Jeff,

with SET STATISTICS IO ON

SELECT TV.Feature, TV.RunStatus, 100.00 * COUNT(*) / B.FeatureCount

:

GROUP BY TV.Feature, TV.RunStatus, B.FeatureCount

:

Mine...

Then it's simple, Jason... Split what get's built for @SQL2 into two or 3 parts based on the number of RunStatuses (60 total) and change the execution to EXEC (@SQL1+@SQL2a+@SQL2b+@SQL2c+@SQL3)......

Heh... I have a real appreciation for that, Jacob... it's called "arrogance" and I usually don't tolerate it. My feeling is that if they want it real bad, maybe...

Exactly what I did in my cross-tab code... nice, job, Koji...

Ok... enough suspense... I'll tell you why... first a review of the dreadful mistake that a lot of developers make. A developer has to solve the problem of returning...

Actually, for the problem I posted, that's absolutely NOT true. Do you know why? 😉

jose (12/6/2007)

---

Hello from Peru 😀 ,

How can i apply this if I'm using sql server 2000? (because the problem of the variable @sql =varchar(8000), in sql server 2000 doesnt...

Actually, that's an old wive's tale... a "Firehose" cursor is...

These should help...

http://www.databasejournal.com/features/mssql/article.php/1462641

http://codebetter.com/blogs/raymond.lewallen/archive/2005/09/12/131869.aspx

http://www.novicksoftware.com/UDFofWeek/Vol2/T-SQL-UDF-Vol-2-Num-41-udf_Sys_RegReadStr.htm

Step 1... take the data provider out to dinner... feed the data provider a nice juicy pork chop... with a slingshot!

Seriously... my first step would be to get the data...

Except for one brief mention somewhere above, everyone is talking about the physical aspects of those things needed to maintain a large database and, of course, all the tricks you...

...and all I really need is a distinct list of what you currently have for RunStatuses...

Did you actually try the code I wrote? Like I said, it should be good for about 132 run statuses... number of features don't matter in this code...