Viewing 15 posts - 32,056 through 32,070 (of 59,102 total)
Brandie Tarvin (11/4/2011)
Evil Kraig F (11/3/2011)
I should learn not to post when I'm typing quickly.
Or when you have the lint ball monster from H3CK watching over your shoulder with it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 7:14 pm
Stefan Krzywicki (11/3/2011)
Each has a GUID primary key.
Unless you defined otherwise, that's likely your problem. Most people define PK's with the default settings and the default settings are to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 7:11 pm
A lot of these problems can be resolved by importing into a staging table using BULK INSERT with OPTION (MAXDOP 1) set. You shouldn't import directly to a final...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 6:34 pm
kramaswamy (11/4/2011)
I've looked for other solutions, but it appears as...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 6:31 pm
Cadavre (11/4/2011)
Steve Kinnaman (11/4/2011)
Could you help me with the next issue: I would like the full path in one column AS Path and the document...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 6:10 pm
Heh... I've seen people do this sort of thing before... decrypt the columns that are being joined on. Bloody expensive and usually not necessary at all. It's much...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 5:34 pm
quongo79 (11/4/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 5:14 pm
Martin Schoombee (11/4/2011)
raotor (11/3/2011)
SELECTCOUNT(Price)
FROMTempSales
GROUP BY Price
ORDER BY Price;
I'm afraid as I'm so green with this forum you'll have to tell me the best way to attach the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 5:08 pm
Cadavre (11/4/2011)
--Standard TestEnvironment of 1,000,000 rows of random-ish data
IF object_id('tempdb..#testEnvironment') IS NOT NULL
BEGIN
DROP TABLE #testEnvironment
END
--1,000,000 Random rows of data
SELECT TOP 1000000 IDENTITY(INT,1,1) AS ID,
RAND(CHECKSUM(NEWID())) * 30000 +...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 5:03 pm
bteraberry (11/3/2011)
I agree with G^2. I would rather error on the side of reducing reads over picking the "fastest" time unless it is really disproportionate.
I'd have to add that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 4:28 pm
Naomi N (11/3/2011)
It is not available in SQL 2008. Does anyone have a code for this SP?
I do. This one (it's older and could use a couple of updates)...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2011 at 7:21 am
I just got done with some testing of my theory that having temporal based and persisted calculated columns in the detail would help this problem. Sure, I get an...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2011 at 7:21 am
Lexa (11/2/2011)
So basically there isn't a situation where CTE will outperform temp table or temp table variable, is that correct?
No. Didn't say that. As with anything else, "It...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2011 at 7:12 am
I'll also tell you this... read the first link in my signature line below and post your data THAT way. You're much more likely to get a coded answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2011 at 10:52 pm
ramanamreddy (11/1/2011)
I don't need any average or sum, I can use it in the query if I want but not in the output,.,.,
Hint: Use MAX for this instead of...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2011 at 10:50 pm
Viewing 15 posts - 32,056 through 32,070 (of 59,102 total)