Viewing 15 posts - 53,341 through 53,355 (of 59,089 total)
...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
Microsoft still uses lightbulbs? 😛 I heard they couldn't find anyone who still knew how, so they've shifted to HI-LEDs that never need changing.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:11 pm
Heh... no, not what we're looking at in Word... Yes, I understand the control character notation for things like ^m (ASCII 13 or Hex OD)... Word seems to have it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 1:31 pm
Better than that, post the first 100 rows of your problem file as an attachment and we'll take a crack at it tonight. Also, post what the CREATE TABLE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 1:26 pm
I'll look at the T-SQL tonight. Not sure yet if there are a wad of cursors. You're saying that would explain the X locks?
Yep... could be... if they're not "Fire...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 1:08 pm
My first inclination about this job is to abandon it... no, I didn't say rewrite it... I do mean "abandon it". This will change the Fill Factor on all...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 12:34 pm
Heh... that about does it for me, Adam... I'm going to pivot the PIVOT command right into Unit 0 and use the old school methods I demo'd for this type...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 12:21 pm
Hard returns are CHAR(13)... Soft returns are actually vertical tabs (CHAR(11))... if that's what you meant...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 12:18 pm
I don't believe that would work on something that looks like this...
"Some Company with a very long name","somedata","some other data"
"Some Company","someData","some other data"
"Some Company with a very long name","some very...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:25 am
Heh... you beat me to it, Noel... I'd rather fix the problem than make a patch and I'm thinking that the problem is just bad code to start with. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:16 am
Viewing 15 posts - 53,341 through 53,355 (of 59,089 total)