Viewing 15 posts - 55,861 through 55,875 (of 59,072 total)
No... but you could place the results of the proc in a temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:58 pm
Heh... now THAT's important... so, lemme ask... is Patient_ID an autonumbering column (or, at least, an incrementing sequence number)?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:40 pm
Heh... just can't bring myself to do that, Serqiy... that would mean I'd have to demo saving the date as an integer that looks like an ISO date or storing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:33 pm
If it's "inline" code, as you say, I've previously told the OP's to use the DATEADD/DATEDIFF method to ensure that there's no chance of an "anomoly" like what appeared in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:28 pm
Bill,
I absolutely agree with writing consistant code and some of the methods to make the code consistant and easy. My only problems with such a UDF are (putting aside speed for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 6:32 am
Not quite what I was after, Peter. Sorry I wasn't clear... was looking to compare the dates in two tables for rows having occurred on the same day.
Serqiy reminded me...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 6:18 am
You must remember that issue with implicit conversion of 0 to date which made that function nondeterministic. |
THAT's what...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 6:12 am
Now... THAT would be quite the trick... anyone know a way to get "date only" and still be able to use an Index SEEK? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2007 at 8:39 pm
Dang... sorry Peter... I keep forgetting to post the results...
===== DateDiff/DateAdd method ======
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2007 at 7:50 pm
You may want to reconsider, Bill... or not
"It Depends" ... ![]()
CREATE FUNCTION dbo.fnDateOnly
/***********************************************************
Purpose:
This function...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2007 at 2:14 pm
Nicely done, Peter... not sure where my post went (must've done the timeout thing
), but I was going to say that your...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2007 at 9:32 am
How do you define "First and Last record"?
If not by date (Dates are not in any particular order according to you), then by...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2007 at 8:46 am
I'm thinking that SQL Server 2k8 kicks some serious butt! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2007 at 12:29 pm
Dang, Peter... you must be working on a really nice box... my poor ol' 1.8Ghz home computer SQL 2k Developer's Edition just didn't do that well... and your's does much better...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2007 at 9:36 am
A bit confused by your original post... what do the two tables contain? One table for FirstNames and one table for LastNames? Or one table for Male and another for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2007 at 9:26 am
Viewing 15 posts - 55,861 through 55,875 (of 59,072 total)