Viewing 15 posts - 51,181 through 51,195 (of 59,091 total)
dmizelle (4/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2008 at 6:53 pm
Hmmmm... what kind of index did you put on the TEXT column?
[font="Courier New"]CREATE TABLE EraseMe (ID INT, WTD TEXT)
CREATE INDEX Dodah ON EraseMe (WTD)
Server: Msg 1919, Level 16, State 1,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2008 at 6:30 pm
Still not going to help on a DATETIME column... A DATETIME column uses only the default system format when displaying data. If you want something else (should be done...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:57 pm
I'd rather have more memory so more data can be cached. Also, no matter how fast the processor is, bad code (usually some form of RBAR) is the great...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:48 pm
alorenzini (4/10/2008)
What would be the best way to get you some sample data?
See the UFL in my signature line for some help on that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:33 pm
Ah... thanks for the explanation, Gail... I just figured it out... the reason they need to do the GROUP BY on a comments column is because they're writing an aggregate...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:58 am
GilaMonster (4/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:49 am
antonio.collins (4/9/2008)
A matrix report will do the pivoting you describe.
Nicely done...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:07 am
Nuh uh... some of us recommend BULK INSERT... BCP would require a trip to the operating system, possibly via xp_CmdShell... that's why I recommended BULK INSERT. I didn't recommend...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:04 am
jezemine (4/10/2008)
Jeff Moden (4/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2008 at 6:00 am
Dumber and dumber is right... they should have left it alone... 2k had a fine optimizer... well, the idiocy started at SP4 which is why I still run sp3a on...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 7:44 pm
Gail (4/9/2008)
here is my query the field is a comment field commentsmc
You're trying to group on a comment field? :blink: As I've asked a couple of times now,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 7:40 pm
Steve's suggestion is good, but use NVARCHAR(MAX) instead... 3rd party either made the original column NTEXT for a reason or because they're stupid... you have to account for either eventuality....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 10:12 am
And a sample of what's in the NTEXT column please... it's hard for me to imagine why you'd want to group on something that can be 4000 bytes long...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 9:47 am
Grant Fritchey (4/9/2008)
But the constant updates from a single spid that is always connected won't act like a transaction & hold that lock open? Just asking, not arguing.
Nope... not if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 8:46 am
Viewing 15 posts - 51,181 through 51,195 (of 59,091 total)