Viewing 15 posts - 38,026 through 38,040 (of 59,072 total)
TheSQLGuru (6/9/2010)
BTW, are you at TechEd this week?
No... I've got one of those major project thingies going on at work.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 8:21 pm
I'm a little late on the feedback after the formatting fix and I apologize for that. VERY nicely done, Wayne. This will help a lot of folks just...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 8:12 pm
Patrick Seegers (6/9/2010)
[font="Courier New"]Are there any opposing views on this usage?Thank you
[/font]
Sure... read the rest of the posts on this thread.
Hmmmm.... "unknown date".... sounds like...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 5:40 pm
Hi Roy,
Heh... I had to laugh a bit because I'm right there with you. Seems the phrase "legacy code" usually means "problem code"... even if it was us that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 6:49 am
Paul_Harvey (6/9/2010)
Thanks for your reply. Yes, my columns are collated as Latin1_General_CI_AS.
Do you think that is the reason? Pity, because it looked like a useful function for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 5:35 am
Just to emphasise what Gail has stated, I've actually seen duplicated data appear thanks to WITH(NOLOCK). I recommend NOT using it most of the time. The proper way...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2010 at 5:29 am
Ok... you can't spell most swear words without vowels and I really don't want someone to get sued because they didn't filter correctly. Here's an 8 character generator that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 8:31 pm
paul_ramster (6/7/2010)
darn flies!
Ah... my apologies for being the messenger. There's more than one fly... here are the results...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 7:55 pm
Yes... I've not been able to force a dupe on a real PK constraint so that's probably not it.
Have you determined that there are actually dupes? If...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 7:40 pm
Sandy2704 (6/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 7:06 pm
ek-822869 (6/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:55 pm
Steve Jones - Editor (6/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:53 pm
Gianluca Sartori (6/4/2010)
rjohal-500813 (6/4/2010)
Likewise Oracle people probably have similar feelings to MSSQL if they have to move to it.
Maybe. What I heard of MSSQL from Oracle DBAs is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:33 pm
jcrawf02 (6/8/2010)
Gianluca Sartori (6/8/2010)
Can anyone take a look at this one?I'm sure my solution sucks and I'm pretty sure the OP is lost and clueless.
Well after that ringing endorsement, let...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:31 pm
Gopi Muluka (6/4/2010)
I think he need this
SET ANSI_NULLS ON
SET ANSI_WARNINGS ON
SET ANSI_PADDING ON
GO
DECLARE@Sample TABLE
(
Code VARCHAR(20) NOT NULL
)
INSERT INTO @Sample
SELECT '22G' UNION
SELECT '10A' UNION
SELECT '45B'
SELECT LEFT(Code,PATINDEX('%[a-z]%',Code)-1)...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:29 pm
Viewing 15 posts - 38,026 through 38,040 (of 59,072 total)