Viewing 15 posts - 43,861 through 43,875 (of 59,097 total)
ben.rosato (5/7/2009)
Jeff Moden (5/6/2009)
[font="Courier New"] USE AdventureWorks
;WITH cteNames AS
(
SELECT FirstName + ' ' + LastName AS FullName
FROM AdventureWorks.Person.Contact
WHERE FirstName + ' ' + LastName LIKE '%[^- .''A-Z]%'
)
SELECT n.FullName,
SUBSTRING(n.FullName,t.N,1) AS BadChar,
t.n AS BadCharPosition,
ASCII(SUBSTRING(n.FullName,t.N,1)) AS BadCharNum
FROM cteNames n
CROSS JOIN Util.dbo.Tally t
WHERE t.N <= LEN(n.FullName)
AND SUBSTRING(n.FullName,t.N,1) LIKE '[^- .''A-Z]'[/font]
I was playing around with this and can't figure out why the "-" in the where clause has to come before all...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:36 am
gserdijn (5/7/2009)
Jeff Moden (5/6/2009)
I can only hope that gserdijn got it from me. 😛
Off course!
When you rewrite a cursor to be set based, don't make the same error in...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:35 am
Jeff Moden (5/7/2009)
Jeff Moden (5/6/2009)
ifila (5/6/2009)
I still get nulls in the Account Table 🙁Thanks
Are all of the files you're trying to import in the exact same format and field order?
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:32 am
Chirag (5/7/2009)
During the interview process i pointed out that...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:13 am
Gianluca Sartori (5/7/2009)
... ooops!I vote for Lynn's solution! There's also an interesting thread on this topic
http://www.sqlservercentral.com/Forums/Topic695508-338-1.aspx
Uh huh... just be careful with what you see in some of the posts...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:05 am
jamiejulius (5/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 11:00 am
GSquared (5/7/2009)
select substring(@String + ',', Number, charindex(',', @String + ',', Number) - Number)
from dbo.Numbers
where Number <=...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 10:58 am
JohnG (5/7/2009)
Jeffrey Williams (5/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 10:41 am
Jeff Moden (5/6/2009)
ifila (5/6/2009)
I still get nulls in the Account Table 🙁Thanks
Are all of the files you're trying to import in the exact same format and field order?
I can help,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 10:34 am
tlehner (5/7/2009)
Steve Jones - Editor (5/7/2009)
However, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 10:16 am
Steve Jones - Editor (5/7/2009)
For the record, I'm a leading commas guy, Jeff is wrong, and it's easier to read. All you trailing comma folk need to change!:-D:-D:w00t:
BWAA-HAA!!! I was...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2009 at 10:14 am
But in this particular SQL statement, there's no reason to alias your tables names - it would just save a few keystrokes, at the cost of making it much less...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2009 at 10:40 pm
aloj (5/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2009 at 10:01 pm
lcardwell (5/6/2009)
I spend a good deal of time 'splaining why certain processes/practices are important and getting folks to think 'out of the box'...
Heh... my most difficult task has been to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2009 at 9:22 pm
Manie Verster (5/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2009 at 7:28 pm
Viewing 15 posts - 43,861 through 43,875 (of 59,097 total)