Viewing 15 posts - 50,566 through 50,580 (of 59,102 total)
Thanks, Sapna... :blush: Such a nice compliment is a great way to start the day. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2008 at 8:01 am
Me too... except I'd add one thing...
UPDATE Employee
SET SocialSecNumber = stuff(stuff(SocialSecNumber , 6, 0, '-'), 4, 0, '-');
WHERE SocialSecNumber NOT LIKE '%[^0-9]%'
... just to be on the safe side.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 11:13 pm
One other thing... why do you want to scramble the dates in such a fashion?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 11:06 pm
"Disater Planning" comes in many forms... this is one of them. You need to make backups that the "IT Member" has no knowledge of and no access to. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 11:01 pm
Million random date pairs in <30 seconds ok?
SELECT SomeDate AS StartDate,
SomeDate+1 AS EndDate
FROM (
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 10:41 pm
Peter, any idea where I can get a list of these ODBC functions?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 6:58 pm
That's if you need a solution for both SQL Server 2000 and 2005... if it's just for 2005, it gets real easy...
SELECT CASE
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 6:45 pm
Au4848 (5/13/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 6:20 pm
Simple case statement should work.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 6:06 pm
I'm sure they're looking for an answer on this one, but my answer would be "None of the above"...
1. All of the updates will cause some improper change...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 6:03 pm
Good documentation and examples of the problem, Ryan!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 4:58 pm
Matt Marston (5/13/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 4:58 pm
benjamin.nelson06 (5/13/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 4:54 pm
srienstr (5/13/2008)
Jeff Moden (5/13/2008)
Why do you need a Cross-Join on the @DistinctQuarters table?
From my read of the code, it appeared to be storing (or intended to store) multiple time frames,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 4:24 pm
quortex (5/13/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2008 at 3:06 pm
Viewing 15 posts - 50,566 through 50,580 (of 59,102 total)