Viewing 15 posts - 46,996 through 47,010 (of 59,101 total)
Peso (11/27/2008)
The query returns 290 columns and joins 62 tables. Under these cirumstances I think 7 seconds is quite good.
Ditto.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2008 at 10:30 am
Mannie, thanks for posting the article... your points are well taken and the appearance of the article is actually very timely for me. It gave me a chance to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2008 at 10:27 am
David Burrows (11/27/2008)
And Jeff makes a good point too. Not enough of you guys get credit for posting knowledge...
Hear, hear. 🙂
But I think we all owe thanks to folks...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2008 at 10:20 am
thisisfutile (11/25/2008)
Jeff Moden (11/25/2008)
Heh... then there's the "intelligent" ones that say things like "performance" doesn't matter and will argue for hours about it. The only reason why I continue...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2008 at 10:17 am
G Bryant McClellan (11/25/2008)
And Jeff makes a good point too....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2008 at 9:49 am
Matt Miller (11/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 10:43 pm
Yep... try getting the TOP 10 random rows from a big table that way... hell to pay for performance. Be careful how you use it for that reason.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 10:17 pm
Here's a "fix" for your code... doesn't change a thing in the code... just the way the "seed" for the RAND function works...
select dbo.fx_getrandomnumber(500, 300, rand(CHECKSUM(NEWID())))
FROM dbo.Tally
WHERE N <= 10
That...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 10:09 pm
Ummm... good idea and nice try... but doesn't work to create different random numbers within the same Select. For example, using the eample Select you have with your...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 10:00 pm
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:29 pm
Either that, or you're mapping doesn't actually equal what's in the file. Could be something stupid like a stray comma in some name in the file.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:25 pm
The data conversion is failing because there's bad data in that column somewhere in the file. You need to find out what the bad data/date is and fix it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:24 pm
That would certainly help... but the OP said he can't touch the code because it's generated by and ERP. This is all vry much a moot issue.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:21 pm
josephptran2002 (11/26/2008)
SELECT COUNT(ClearedDate) AS 'Month',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:15 pm
When you get done with your CLR, lemme know...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2008 at 9:09 pm
Viewing 15 posts - 46,996 through 47,010 (of 59,101 total)