Viewing 15 posts - 41,776 through 41,790 (of 59,067 total)
Heh... ok. I just did a preview of the book on Amazon. They called it a "Pivot" table because of it's use in splitting data from a single...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 1:17 pm
Thanks for the feedback, Greg.
About 95% of what I do with Tally tables need a Tally table that starts with 1. That's why I haven't started mine at 0....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 1:06 pm
You've missed my point. I realize that Column C needs to be in ascending order. Does the order in which they appear according to column B need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 12:56 pm
raaz66 (9/25/2009)
I want to convert number into words in sql server 2005.For examople,we enter number like 15000 from front end ,but it should be save into database like...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 11:19 am
Yes... step 1 would be to post some data in a readily consumable format. That will do two things... it'll let us see the type of data you're trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 11:16 am
It's not possible unless you have another column that maintains the order of the original data or you aways want the data in descending order according to column B (according...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2009 at 10:57 am
That's a shame... Hugo's code fixes the problem and you would have seen it.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2009 at 11:09 am
DavidL (9/25/2009)
And no - there is no reason to use ORDER BY every time you use the tally table. There is reason to use ORDER BY every time you expect...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2009 at 10:59 am
DavidL (9/25/2009)
Jeff, I'm sure you never expected anyone to up and create a tally table with 16m records, but, there I was with a slow afternoon on my hands...
Heh... it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2009 at 10:03 am
I get it... you're not running the same code as in the article. Please post the code you are running. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 5:56 pm
I ran your code from the previous post... here it is, again...
select getdate()
select dbo.CalcTimeBetweenTwoDates('2004-11-16 15:30', '2007-11-21 07:31')
select getdate()
Here's what I get for an error message from that code...
Msg 4121, Level...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 5:51 pm
Thanks for the feedback, Mazharuddin... I'll take a look.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 5:41 pm
David Kranes (9/24/2009)
Here is the DDL. Thank you.
There real problem is that the "Active_Address_ID" has no index on it nor is it a part of any other index, yet...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 5:19 pm
Almost forgot... if you're just playing with a Tally table, then TempDB is fine. If you want one for a production table, then Hugo is correct there... TempDB is...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 5:02 pm
DavidL (9/24/2009)
DECLARE @DateStart DATETIME
DECLARE @DateEnd DATETIME
--===== Find the min and max dates in the range of data
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2009 at 4:59 pm
Viewing 15 posts - 41,776 through 41,790 (of 59,067 total)