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...

Steve, if you come anywhere near Detroit, let me know... I gotta meet you some day and it's not likely I'll make it out to your farm!

And congrats on making...

PLEASE don't double post anymore... spreads resources too thin.

http://www.sqlservercentral.com/Forums/Topic436548-146-1.aspx

PLEASE don't double post anymore... spreads resources too thin.

http://www.sqlservercentral.com/Forums/Topic436564-5-1.aspx

Please don't double post... spreads resources too thin.

http://www.sqlservercentral.com/Forums/Topic436885-146-1.aspx

Here's a slightly better rendition based on what you just posted...

Should be good for about 132 columns of RunStatuses not including Feature.

DROP TABLE Raw

GO

CREATE TABLE Raw (TestListID INT, Feature VARCHAR(256),...

...and, you're saying this didn't work?

CREATE TABLE Raw (TestListID INT, Feature VARCHAR(256), RunStatus VARCHAR(64),

...

Are you saying that you'd rather have the run status in columns instead of rows?

In other words, each row would be a Feature and each column would be a RunStatus...

... and are you saying that the query you posted is returning the data you want in the format you want it in?

I can help on the Pivot... but your real performance problem may be the view. If you do a SELECT TOP 10 from the view, how long does it...

Understood about the security thing... lemme see what I can dig up for an example...

Heh... my concern is that UDF's of this nature qualify as RBAR... you get to split exactly one row. That's fine for a single parameter passed in from a...