Viewing 15 posts - 36,316 through 36,330 (of 59,067 total)
mm.sailaja (10/18/2010)
I know that a table is an unordered. Order by clause gives us the result in a sorted manner. I don't want the result in a sorted order....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2010 at 5:48 am
gunapriyan (10/17/2010)
Thanks for your reply.
Actually I am developing a software with the help of VB 6.0 and SQL Server 2005.
In Date Part, Initially i have put DateTime Picker...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2010 at 5:43 am
Paul White NZ (10/18/2010)
SELECT *
FROM #membership...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2010 at 5:10 am
Dave Ballantyne (10/18/2010)
I would be interested in comparative performance over a larger dataset. 😉
No problem. Here's some test data...
--===== Expand the test data using "lasagne" copies of the original...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2010 at 5:06 am
SQL* (10/17/2010)
How to make use of UDF or subquery?Which is better one with performance considerations?
thanks
"It Depends". You have to test each way based on the situation you're trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 11:07 pm
My recommendation is to lookup the word REPLACE in Books Online. It'll show you how to easily do such a thing. I'd show you the actual code but...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 11:02 pm
Although having two systems come up with the same GUID is a bit like having two comets appear in the same mile across 14 quadrillion Milky Way galaxies, it can...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:57 pm
Eric Russell 13013 (10/12/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:51 pm
Grant Fritchey (10/12/2010)
They should be used where appropriate...
I apologize for puting you on the spot but what do you consider an appropriate use for them is especially since even MS...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:49 pm
The answer is the same answer as to anything else... "It Depends".
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:44 pm
Ah... sorry... didn't see the age of the thread or the recent jump in. Still, what I wrote is true. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:37 pm
JC-3113 (6/29/2009)
I am looking at your code for tempdb files
I am new to sqlserver 2005
Not up to speed on TEMPDB files yet
i understand the creation of the multiple tempdb#.mdf...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:35 pm
CELKO (10/17/2010)
Read Codd's Information Principle, so you will see what a stupid question this is. An...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:32 pm
WayneS (10/17/2010)
Jeff Moden (10/17/2010)
WayneS (10/17/2010)
This works, but the performance is atrocious.
Because of the very large datespan from any date in this century to 9999-12-31, I'm thinking that my ol' friend...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:23 pm
WayneS (10/17/2010)
Jeff Moden (10/17/2010)
Sorry... forgot to print out the results...
MemberIDStartDateEndDateGap
12006-10-01 00:00:00.0002007-12-31 00:00:00.0000
12008-01-15 00:00:00.0002008-12-31 00:00:00.00015
22007-02-03 00:00:00.0002007-12-31 00:00:00.0000
22008-01-15 00:00:00.0002008-12-31 00:00:00.00015
32006-10-01 00:00:00.0002007-09-30 00:00:00.0000
32008-01-01 00:00:00.0002008-12-31 00:00:00.00093
Jeff, are these gaps correct? By my calc, there...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:10 pm
Viewing 15 posts - 36,316 through 36,330 (of 59,067 total)