Viewing 15 posts - 36,331 through 36,345 (of 59,067 total)
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 the Tally Table...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 10:06 pm
Sorry... forgot to print out the results...
MemberIDStartDateEndDateGap
12005-10-01 00:00:00.0002006-09-30 00:00:00.0000
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
12009-01-01 00:00:00.0009999-12-31 00:00:00.0000
22005-10-01 00:00:00.0002006-09-30 00:00:00.0000
22006-10-01 00:00:00.0002007-09-30 00:00:00.0000
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
22009-01-01 00:00:00.0009999-12-31 00:00:00.0000
32005-10-01 00:00:00.0002006-09-30 00:00:00.0000
32006-10-01 00:00:00.0002007-09-30 00:00:00.0000
32008-01-01 00:00:00.0002008-12-31...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 9:57 pm
TheSQLGuru (10/17/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 9:53 pm
Doug Lane (10/13/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 7:37 pm
Steve Jones - SSC Editor (10/14/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 7:04 pm
WayneS (10/14/2010)
"Don't try this at home... we're professionals!"
Heh... I have the perfect SQL subject for that... Quirky Update. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:57 pm
Heh... screw it. If you really insist on doing it using RBAR, do it in C#. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:47 pm
WayneS (10/16/2010)
GilaMonster (10/16/2010)
Me: Run CheckDB and and post the full and unedited results
OP: I have used that command and it returned about 3000 line of error code. This is...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:40 pm
GSquared (10/15/2010)
CirquedeSQLeil (10/15/2010)
GSquared (10/15/2010)
Then I realized it would contain at...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:37 pm
Alvin Ramard (10/15/2010)
Grant Fritchey (10/15/2010)
GilaMonster (10/15/2010)
<headdesk><headdesk><headdesk><headdesk>
(No, I'm not going into details, it's a little too sensitive a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:34 pm
I'm not a GUI/App programmer so I'll have to find another way to test what you propose, Solomon. Shouldn't be too difficult, though.
If I were an App programmer, I'd...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 6:19 pm
Gosh... my first take on this is all the people in this discussion citing XML as a good way to do this. Would you folks mind providing a little...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 3:51 pm
Daniel Macey (8/18/2009)
Although, with SQL Server 2008 around, I am surprised that you did not mention the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 3:41 pm
olimp23 (10/15/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2010 at 3:39 pm
CELKO (10/14/2010)
Jeff Moden (10/13/2010)
[font="Courier New"]Msg 207, Level 16, State 1, Line 18
Invalid column name 'part_id'.
Msg 245, Level 16, State 1,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2010 at 8:13 am
Viewing 15 posts - 36,331 through 36,345 (of 59,067 total)