Viewing 15 posts - 52,051 through 52,065 (of 59,102 total)
I have to know because it's a bit unusual... why do you need this type of sort?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2008 at 7:49 am
Cool. Thanks for posting the solution!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 9:31 pm
Mike C (3/6/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 9:24 pm
How does your process work for files like this?
I don't believe it was meant to... wasn't advertised that way except maybe by a slightly misleading title.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:52 pm
Very cool... thank you for the stats and the feedback, John.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:48 pm
That's useful... thank you very much.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:46 pm
Yep... I gotta agree with that. Like I said, it's the classic solution and it's pretty darned fast to boot. And, like you said, it works on both...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:36 pm
Care to take another crack at it? 🙂
Why shore'nuf! 😀
You know... you're absolutely right... if the original requirement was to return ALL columns and ALL rows for ALL...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:25 pm
Sure am sorry about that... Task Pad has always been a little quirky in 2k.
If you really want to know those values, try the following
USE TEMPDB
EXEC dbo.sp_HelpFile
EXEC dbo.sp_SpaceUsed
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 6:19 pm
Grant Fritchey (3/6/2008)
Jeff Moden (3/6/2008)
Grant Fritchey (3/5/2008)
What this is doing is using the temp table in place of a join or joins. That's bad.
Ummm... I gotta say, "Not always"....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 6:03 pm
doug@scalabilityexperts (3/6/2008)
Preach on brother! Amen and halleluah!
Heh... dang, Doug! You fit right in with me an all the other crazies 🙂 ... and it didn't even take you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 5:44 pm
Make that 3... it looks like they also fixed the non-wrapping problem on long thread names!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 5:34 pm
Jeff Moden (3/6/2008)
DROP TABLE mm_CompanyNo
DROP PROCEDURE GetNextCustNo
GO
--==============================================================================================
-- Setup for the test
--==============================================================================================
--===== Create sequence table...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 5:07 pm
Nah... they need an absolute Ninja, Sam... they want to let everyone run rough shod over the database and the server but still keep it running. They need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 4:42 pm
Jacob Luebbers (3/6/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 4:37 pm
Viewing 15 posts - 52,051 through 52,065 (of 59,102 total)