Viewing 15 posts - 56,401 through 56,415 (of 59,069 total)
Considering that only two rows of a table are being accessed for the original question being asked, I'd have to say the delta-t would be measured in nano-seconds. The big...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 7:19 am
LOL! This is where I'm supposed to say something like "Do it in the app"...![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:44 am
So, explain the code Gail wrote for you... I wanna make sure you actually learned something other than how to get other people to do your work for you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:41 am
Figured the original poster wouldn't have gotten a thing out of it... you know... the "flying pig" thing... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:39 am
Ooooowwww.... why on Earth do you want to do this? Even if it's just a report, if someone needs to ananlyze the data using any form of aggragation, they're pretty...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:36 am
>>i geting problem.
Any chance of you describing what that problem is? Error message? ???? You might get people to help a bit quicker that way...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:21 am
Sam,
I don't work with multi-lingual databases so I've no example for you. However, COLLATE is the answer you are looking for... take a look in Books Online for COLLATE.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:19 am
This is a very "old" problem and there must be a thousand or so posts on how to do this on this forum alone (search does work)... but, here it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 6:15 am
Not sure, Gail, but I think you just did someone's "urgent" homework for them... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 5:59 am
I'm right there with Serqiy... I use system functions whenever I can...
I'll probably get my head handed to me for using undocumented features but I believe this works both...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 5:34 am
That also takes care of the problem when unpredictable lengths occur without a hint of a loop. Nicely done!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 5:25 am
| By checking the string against the '%[^0-9A-F]%' pattern, I've tried to avoid any possibility of SQL Injection due... |
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 5:21 am
Heh... I thought you said "without looping".
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 5:17 am
Nicely done... If I may suggest, however, a method that avoids both loops and dynamic SQL...
--===== If the test table exists, drop it
IF OBJECT_ID('TempDB..#HexToAlpha','U') IS NOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 12:49 am
He doesn't get it as a hex/binary number... he get's it as a string.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2007 at 12:17 am
Viewing 15 posts - 56,401 through 56,415 (of 59,069 total)