Viewing 15 posts - 40,486 through 40,500 (of 59,072 total)
Never mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 4:30 pm
Nah... nothing so superior or diligent... I had the need to visit my Tally table article and it popped up on the right as a related "FORUM" entry.
Some of these...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 4:03 pm
Karthik,
I know this is an old post but just a couple of tips here... I noticed you have the following...
If @ID =''
Begin
Select @ID = Null
End
If @sp-2=''
Begin
Select @sp-2 = Null
End
If @ClassId...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 3:39 pm
SwePeso (5/29/2008)
Did you try my latest suggestion then?
Heh... considering the date of that post and today's date, I'm thinking that requires some little thought, eh? 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 3:35 pm
Heh... like Jackie Chan's Uncle says in the cartoon, "And one mo ting!"
There is a way to totally obfuscate the cross-joins if you ever need to do such a thing......
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 3:26 pm
Dugi, thanks for the kudo but it's not mine alone... take a look at the "credits" on that thing... lots of folks had some great ideas that improved the great...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 3:14 pm
Heh... and for those who are mildly curious as to what Rev 03 may have been... I ran into a human stone wall who would not allow code to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 3:03 pm
Nabha is spot on and, if you check out the link he posted, you'll find the "Tally" table is a pretty nice replacement for the spt_Values table and has a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 2:46 pm
TheSQLGuru (12/24/2009)
run an insert from SSMS with set statistics on and show actual execution plan. My best guess is that one...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 11:13 am
freeman.e.l (12/23/2009)
this is probably caused by a large number of indexes.
Absolutely spot on, Freeman.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 11:02 am
Ah... one other thing... just to prove that it works across multiple month boundaries and even year boundaries, here's a change in the data. My recommendation would be that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 10:46 am
Prakash-485822 (12/23/2009)
Please find below the data
MonthStart MonthEnd MonthTotalDaysAmount
Mar3/9/09 0:003/13/09 0:004 71
Mar3/23/09 0:004/5/09 0:0014 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 10:14 am
freeman.e.l (12/24/2009)
The question was not clear by any means. Additionally, the second example does not have a logical relationship that holds true for Start Date, End Date and TotalDays.
I thought...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 9:58 am
MonthStart MonthEnd MonthTotalDaysAmount
Mar3/9/09 0:003/13/09 0:004 71
Mar3/23/09 0:004/5/09 0:0014 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 2:08 am
arun.sas (12/24/2009)
Hi Jeff,But still am using the @@IDENTITY, yet no issue raised, ok will check your advice.
Ah... sorry, my bad.l I just started reading your code more in depth...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2009 at 2:03 am
Viewing 15 posts - 40,486 through 40,500 (of 59,072 total)