Viewing 15 posts - 53,341 through 53,355 (of 59,098 total)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:51 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:41 pm
...and all I really need is a distinct list of what you currently have for RunStatuses...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:04 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:01 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:40 pm
PLEASE don't double post anymore... spreads resources too thin.
http://www.sqlservercentral.com/Forums/Topic436548-146-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:35 pm
PLEASE don't double post anymore... spreads resources too thin.
http://www.sqlservercentral.com/Forums/Topic436564-5-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:34 pm
Please don't double post... spreads resources too thin.
http://www.sqlservercentral.com/Forums/Topic436885-146-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:30 pm
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),...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:27 pm
...and, you're saying this didn't work?
CREATE TABLE Raw (TestListID INT, Feature VARCHAR(256), RunStatus VARCHAR(64),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:16 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:32 pm
... and are you saying that the query you posted is returning the data you want in the format you want it in?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 8:02 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 8:00 pm
Understood about the security thing... lemme see what I can dig up for an example...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:00 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:53 pm
Viewing 15 posts - 53,341 through 53,355 (of 59,098 total)