Viewing 15 posts - 35,731 through 35,745 (of 59,102 total)
CELKO (12/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 4:09 pm
CELKO (12/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 2:56 pm
Just a personal opinion here... I don't believe in such canned tests because they're not testing for what I want to see in a Developer or DBA.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 2:38 pm
Remove autoshrink? No... I never use it and probably never will. I also can't think of a reason why I'd ever use it. But it takes MS...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 2:24 pm
Also, if you post data as outlined in the article at the first link in my signature line below, you might even get someone to provide a tested, coded answer....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:49 pm
Bharat Panthee (12/11/2010)
if shorttime in hh:mm format then just used:select CAST((cast((datediff(minute,[EmpSIN],[EmpSOut])-datediff(minute,[FirstIn],[FirstOut]))/60 as varchar(10))+ ':' + cast((datediff(minute,[EmpSIN],[EmpSOut])-datediff(minute,[FirstIn],[FirstOut]))% 60 as varchar(10))) AS TIME),
Heh... I guess "No replies to this thread please"...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:45 pm
Never mind... someone posted an answer on the cross post at http://www.sqlservercentral.com/Forums/Topic1033293-145-1.aspx even though Gail asked folks to post here.
Moving on.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:41 pm
pnasz (12/11/2010)
In this computed column i want to display the result in hh.mm
empid FirstIn FirstOut EMPSIN EMPSOut hrworked shorthr
100 08:35:00 18:01:00 08:00:00 18:00:00 9.26 0.74
firstin,firstout...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:37 pm
anitha.chacko (12/11/2010)
Pls help me.How to create a package in SQL Server 2000
If the reference of "package" means like the ones in Oracle, you don't. SQL Server has no equivalent.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:31 pm
Digs (12/11/2010)
Thanks Jeff..Progress has been good since our last chat !:-):-D:-)
Very cool. Thanks for the feedback on that.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:29 pm
ChrisM@home (12/11/2010)
Good Lord, I've been reincarnated as Jeff's fluffer!
Heh... a fine fluffer you'd be indeed. 😛 But it wasn't that. You posted right after I started my...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 1:28 pm
Digs (12/11/2010)
All I need is a guru to spend 1 sec of his time to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 12:34 pm
Thanks for the readily-consumable data and the great description of the problem.
First, I added a necessary column to the Temp table during its creation...
IF OBJECT_ID('tempdb..#priceData') IS NOT NULL DROP TABLE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 12:18 pm
NICE! Well done, Craig! This is one of those that should be required reading... especially for recruiters, job seekers, and managers that don't have an SQL background.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2010 at 6:01 am
JKSQL (12/9/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2010 at 7:26 pm
Viewing 15 posts - 35,731 through 35,745 (of 59,102 total)