declare @n varchar(40)

set @n = 'Johnson Sr., John Richard'

SELECT LEFT(@n,CHARINDEX(',',@n)-1) LastName,

PARSENAME(REPLACE(STUFF(@n,1,CHARINDEX(',',@n)+1,''),' ','.'),2) FirstName,

PARSENAME(REPLACE(STUFF(@n,1,CHARINDEX(',',@n)+1,''),' ','.'),1) MiddleName

--Jonathan

Just yesterday...

http://www.sqlservercentral.com/forum/link.asp?TOPIC_ID=18145

--Jonathan

quote:

---

This statement will not work for dates that fall in the year 2000. Which is the best way to do for...

The best practice is to use stored procedures as command objects with parameter objects at the front end. This is fastest, most secure, and doesn't require any string conversions...

Explained at the end of this article:

http://support.microsoft.com/?id=207187

--Jonathan

quote:

---

Also note that you're going to cough up half your physical RAM to the OS. If your SQL box has 4GB...

quote:

---

Thank you, Jonathan. You are right. The compatibility level is 65. What determines the compatibility level? What can be done to make...

Why use UNION if you don't need to? A query like the one I posted will both perform better and be less wordy.

--Jonathan

Check the compatibility level with sp_helpdb. If it's less than 80, you can't use collations on columns.

--Jonathan

quote:

---

We are running SQL Server 2000, SP3 Standard Edition on Windows Server 2000 SP4 with 4 gig of memory and a 4...

quote:

---

I was mistaken. We use this process for two main reasons:

1. If we have to change NULL to NOT NULL

2. For SQL...

If you're using SQL Server 7 or SQL Server 2000, just use ALTER TABLE to add a new column.

--Jonathan

quote:

---

OK still can't get it to work. Here is a simular example of what I'm doing using the Northwind database.

This is the...

SELECT YEAR(GETDATE())*1000+DATEPART(y,GETDATE())

--Jonathan

quote:

---

You don't say anything about the quality of

I work with a lot of crappy name & address info we get from...