Viewing 15 posts - 44,641 through 44,655 (of 59,095 total)
dmoldovan (3/12/2009)
Try also:CONVERT(CHAR(8), GETDATE(), 114)
CONVERT(CHAR(8), GETDATE(), 108)
No... not for the application the OP is going to use and almost never for everything else because both methods are slow due to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2009 at 6:50 pm
karthikeyan (3/11/2009)
if you see REVERSE() is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2009 at 12:30 am
First of all... very well written article. Nice to see examples like that with some performance stats. Unfortunately, the most important performance for the user (duration) wasn't measured...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2009 at 12:18 am
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 9:33 pm
Bob Hovious (3/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 9:28 pm
aram_golbaghi (3/11/2009)
hii think gsquare's solution is verywell,
works fine
Yep... right up until you dial a 1 or 3 digit country code instead of +44.
Country codes can be from 1 to 3...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 9:05 pm
Spikemarks (3/11/2009)
Once I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 8:59 pm
Heh... close... the next question will likely be "How can I parameterize the TOPs in SQL Server 2000?"
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 8:42 pm
Tony (3/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 8:11 pm
sumit-saini (2/16/2009)
Thanks for the code, but i will be test the code tommorrow @ my work and i will be able to tell you the performance of this logic...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:55 pm
Sorry for the late reply. My answer would be "Nope... I'll use a temp table"... just wanted folks to know that it could actually be done.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:45 pm
KT8177 (3/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:39 pm
Heh... nope... see above where I posted...
SELECT ID
FROM #Test
WHERE Countries IN ('IN','AU')
GROUP BY ID
HAVING COUNT(*) = 2
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:33 pm
Heh... thanks for posting your solution. I guess that's why I don't like DTS or SSIS... T-SQL makes it so much simpler...
DECLARE @SomeDate VARCHAR(8)
SET @SomeDate...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:30 pm
That was the first question... now, let's see if the final question about this comes up. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2009 at 7:25 pm
Viewing 15 posts - 44,641 through 44,655 (of 59,095 total)