Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can probably do better than this using the SQL# functions, but in straight T-SQL, here you go.</p> <p>The main idea here is to parse out the last segment/token in the name using <code>REVERSE</code> and <code>PATINDEX</code>, and then match it to a list of known suffixes.</p> <p>First some test data:</p> <pre><code>IF OBJECT_ID('tempdb..#names') IS NOT NULL DROP TABLE #names IF OBJECT_ID('tempdb..#suffixes') IS NOT NULL DROP TABLE #suffixes CREATE TABLE #names (name VARCHAR(32)) CREATE TABLE #suffixes (suffix VARCHAR(32)) GO INSERT #names VALUES ('BRUNNING, II' ) INSERT #names VALUES ('BURCH II' ) INSERT #names VALUES ('BUSS, JR.' ) INSERT #names VALUES ('CANI III' ) INSERT #names VALUES ('CHRISTIAN,SR' ) INSERT #names VALUES ('COLVIN Jr' ) INSERT #names VALUES ('COWHERD,JR.' ) INSERT #names VALUES ('BILLY BOB' ) INSERT #names VALUES ('JOHNNY' ) INSERT #suffixes VALUES ('II' ) INSERT #suffixes VALUES ('III') INSERT #suffixes VALUES ('JR' ) INSERT #suffixes VALUES ('SR' ) </code></pre> <p>Then, an inline <code>SELECT</code> version. Notice the use of <code>NULLIF</code> to control for <code>SUBSTRING</code> errors.</p> <pre><code>SELECT name , left_segments , right_segment , new_name = CASE WHEN b.suffix IS NOT NULL THEN a.left_segments ELSE a.name END , b.suffix FROM ( SELECT name , left_segments = CASE WHEN left_segments LIKE '%[ ,]' THEN LEFT(left_segments,LEN(left_segments)-1) ELSE left_segments END , right_segment = CASE WHEN right_segment LIKE '%[.]' THEN LEFT(right_segment,LEN(right_segment)-1) ELSE right_segment END FROM ( SELECT * , left_segments = RTRIM(LEFT(RTRIM(name),LEN(name)-NULLIF(PATINDEX('%[ ,]%',REVERSE(RTRIM(name))),0))) , right_segment = RIGHT(RTRIM(name),NULLIF(PATINDEX('%[ ,]%',REVERSE(RTRIM(name))),0)-1) FROM #names ) a ) a LEFT JOIN #suffixes b ON a.right_segment = b.suffix </code></pre> <p>Alternately, <code>UPDATE</code> w/ local vars:</p> <pre><code>ALTER TABLE #names ADD left_segments VARCHAR(64) , right_segment VARCHAR(64) GO DECLARE @name VARCHAR(64) , @len INT , @last_delim INT , @left_segments VARCHAR(64) , @right_segment VARCHAR(64) UPDATE #names SET @name = RTRIM(name) , @len = LEN(@name) , @last_delim = @len-NULLIF(PATINDEX('%[ ,]%',REVERSE(@name)),0) , @left_segments = RTRIM(LEFT(@name,@last_delim)) , @right_segment = RIGHT(@name,@len-@last_delim-1) , @left_segments = CASE WHEN @left_segments LIKE '%[ ,]' THEN LEFT(@left_segments,LEN(@left_segments)-1) ELSE @left_segments END , @right_segment = CASE WHEN @right_segment LIKE '%[.]' THEN LEFT(@right_segment,LEN(@right_segment)-1) ELSE @right_segment END , left_segments = @left_segments , right_segment = @right_segment SELECT a.* , new_name = CASE WHEN b.suffix IS NOT NULL THEN a.left_segments ELSE a.name END , suffix = b.suffix FROM #names a LEFT JOIN #suffixes b ON a.right_segment = b.suffix </code></pre> <p>The inline <code>SELECT</code> is fairly convenient, but difficult to read and troubleshoot. I prefer the <code>UPDATE</code> with local vars for anything I might have to return to later. Plus, it makes individual edits easier to apply.</p> <p><strong>EDIT</strong>, <code>SELECT</code> method, slightly edited, and wrapped in an <strong>inline table-valued function</strong>. A inline TVF should be more efficient than a scalar UDF, and you get multiple return values to boot.</p> <pre><code>CREATE FUNCTION dbo.ParseNameAndSuffix (@name VARCHAR(64), @ValidSuffixes VARCHAR(512)) RETURNS TABLE AS RETURN ( SELECT left_segments , right_segment , new_name = CASE WHEN CHARINDEX(';'+right_segment+';',';'+@ValidSuffixes+';') &gt; 0 THEN a.left_segments ELSE a.name END , suffix = CASE WHEN CHARINDEX(';'+right_segment+';',';'+@ValidSuffixes+';') &gt; 0 THEN a.right_segment END FROM ( SELECT name , left_segments = CASE WHEN left_segments LIKE '%[ ,]' THEN LEFT(left_segments,LEN(left_segments)-1) ELSE left_segments END , right_segment = CASE WHEN right_segment LIKE '%[.]' THEN LEFT(right_segment,LEN(right_segment)-1) ELSE right_segment END FROM ( SELECT name , left_segments = RTRIM(LEFT(name,LEN(name)-NULLIF(PATINDEX('%[ ,]%',REVERSE(name)),0))) , right_segment = RIGHT(name,NULLIF(PATINDEX('%[ ,]%',REVERSE(name)),0)-1) FROM (SELECT name = LTRIM(RTRIM(@name))) a ) a ) a ) GO SELECT * FROM #names a CROSS APPLY dbo.ParseNameAndSuffix(a.name,'II;III;JR;SR') b </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POTSQL Statement to move Name Suffix (Jr, Sr, IV, etc) into another field
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter Radocchia
    1. USPeter Radocchia
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTSQL Statement to move Name Suffix (Jr, Sr, IV, etc) into another field
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is outstanding! One last request if you are able to do this. Would it make sense to have this as a FUNCTION too? I am assuming you would just modify the SELECT version name ParseLastName with the In being the LastName and the Out being NewLastName and the Suffix. I know for readability it would be much nicer.
      singulars
      1. PO
      1. USGerhard Weiss
    2. CO*Very* good idea. I've wrapped it in a inline TVF. Readability, performance, and multiple return values all in one.
      singulars
      1. PO
      1. USPeter Radocchia
    3. COYou da man Peter!!!
      singulars
      1. PO
      1. USGerhard Weiss
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload