Viewing 15 posts - 49,366 through 49,380 (of 59,091 total)
Also, try Decimal(38,0) or BIGINT....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2008 at 4:18 am
alijaffaromran (7/7/2008)
I want to create a table X1 with a datetime field StartDate and format it as "dd-mmm-yyyy hh:mm:ss". Is defining the format of a field possible?
For way to many...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 7:32 pm
annas (7/7/2008)
This is my first post here and I hope this is not an insanely stupid question, but how does N recieve values in the function listed by Jeff?...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 7:15 pm
sqlservercenter (7/7/2008)
shrink it at each weekend.
Absolutely not... it's just going to grow again and all you're doing by shrinking it is cause fragmentation of the underlying files at the OS...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 5:13 pm
Tomm Carr (7/7/2008)
alter table dbo.CallCost
add Seconds as DateDiff( ss, 0, '1900-01-01 ' + Duration );
Now you have a computed column which very quickly, and behind the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 5:11 pm
Heh... translation... BOOOOOM! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 5:03 pm
B.A. Cooper (7/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 5:00 pm
Ok... now, to understand how the function works, you have to read the following...
http://www.sqlservercentral.com/articles/TSQL/62867/
If you want a super deep knowledge of how to do splits well beyond what's in that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 10:19 am
mick burden (7/7/2008)
DECLARE @Now...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 10:16 am
If you're not going to finish it, you shouldn't start it. 😉 What do you want to race on... again? 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:25 am
Lynn Pettis (7/7/2008)
Just one little problem with your code above. The closing paren for the CREATE TABLE #FileDetails is included in your comment. It took me a bit...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:23 am
Steve Jones - Editor (7/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:18 am
I don't know why folks say that CLR's perform better and are more scalable... it's absolutely not true in about 99% of the cases and several of us have beat...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:13 am
You're right... it's an awesome study! Proves what I've been saying all along about some folks in the IT business... they don't look, they don't read, they don't understand......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:58 am
Part of the problem is that you're not measuring time correctly... you're including the time it takes for Barry to build his example... I added a bit to Barry's existing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:51 am
Viewing 15 posts - 49,366 through 49,380 (of 59,091 total)