Viewing 6 posts - 1 through 6 (of 6 total)
Yeah, I saw that after I posted my response. Thanks!
April 30, 2009 at 1:50 pm
Nevermind, as I look at it closer, I see your point. Thanks for the correction.
Blessings!
Amber
April 30, 2009 at 1:33 pm
DECLARE @CurrentDate DATETIME
SET @CurrentDate = GETDATE()
DECLARE @Sample TABLE
(
SomeID INT IDENTITY(1,1)
,SomeDate DATETIME
)
INSERT INTO @Sample
SELECT '2009-04-30 18:29'
UNION ALL SELECT '2009-04-30 10:29'
UNION...
April 30, 2009 at 1:29 pm
I'm not going to argue with you about this. I've been using dateadd(day, 1, date) for about six months and I use it in many different programs and stored...
April 30, 2009 at 12:46 pm
Hi Jeff,
The dates I use do have a time with them (that is how SQL stores them) and dateadd(day, 1, date) still works fine.
Thanks!
Amber
April 30, 2009 at 11:53 am
I discovered this several months back, but I use: dateadd(day,1,) as my fix. Just another way of doing it.
This is VERY useful information! Thanks for posting...
April 29, 2009 at 12:23 pm
Viewing 6 posts - 1 through 6 (of 6 total)