Viewing 15 posts - 35,671 through 35,685 (of 59,099 total)
hemanth T (12/16/2010)
hi,thanks for your advice.surely i will not use caps hereafter,and also thank you for the solution u gave to my scenario.:-)
Thanks for the feedback, hemanth. And...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2010 at 6:55 am
Learner1 (12/10/2010)
I got the answer anyways,,,using Recursive CTE
IMHO... [font="Arial Black"]ABSOLUTELY NOT!!! [/font]:-P
While it certainly is easy to write an rCTE to do this, an rCTE will use a heck of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 11:54 pm
Heh... first... the use of all caps usually ticks people off because it's an indication of yelling on these forums. Just so you know. 😉
Second, I'll let the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 11:50 pm
There's another disadvantage to using CEILING for this problem... if you divide first using a NUMERIC number such as 1000.0 and the original number was an INT, the result won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 10:24 pm
andrewd.smith (12/15/2010)
Jeff Moden (12/15/2010)
parthi-1705 (12/13/2010)
But i want to know only CEILING can do this or some other functions can do this or notThanks
Parthi
CEILING is the way people do it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 10:06 pm
ASDL (12/15/2010)
My options are Method 2 and Method 3, I'll choose #3 (SELECT * query) because it is simple and AFAIK I would get...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:49 pm
WayneS (12/15/2010)
[Sigh]So many people need to see my presentation... maybe at SQL Rally??? I'm counting on you guys to vote for it next month!
[/Sigh]
I absolutely agree with that. Lot's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:38 pm
Tom.Thomson (12/15/2010)
Jeff Moden (12/14/2010)I'm not sure I'd call them dangerous (by themselves, they won't cause any damage, I think) but they sure are false. Heh... it's proof positive that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:37 pm
jigneshdpatel (12/15/2010)
Is SQL Server Team listening?
Nah... probably not. What's important is that people who use T-SQL everyday are. 🙂
I noticed that this was your first post. Let...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:28 pm
CirquedeSQLeil (12/15/2010)
Thanks Jeff. This is functionality that I have yet to use.
You bet, Jason, and thanks for stopping by. Hopefully I've given most folks incentive to continue to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:26 pm
UMG Developer (12/15/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:24 pm
mtassin (12/15/2010)
Thanks a lot Jeff... as I said before, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:20 pm
alen teplitsky (12/15/2010)
which...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:18 pm
Tom Bakerman (12/15/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:14 pm
Heh... I just can't keep up. It would appear you folks found the thread we were talking about.
BTW... I don't use FLOAT anymore either. Too many people were...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2010 at 9:00 pm
Viewing 15 posts - 35,671 through 35,685 (of 59,099 total)