Split FullName column

Question

-- Create table dbo.FullNameTest
IF OBJECT_ID('FullNameTest') IS NOT NULL BEGIN
DROP TABLE dbo.FullNameTest;
END;
CREATE TABLE FullNameTest
(ID INT Not Null IDENTITY
, FullName NVARCHAR(80) Not Null
, CONSTRAINT PK_ID PRIMARY KEY CLUSTERED(ID)
GO
INSERT INTO FullNameTest
VALUES('Mr Hog Finn Gad'),('Grace Bruce'), ('Dr.Paul'), ('Master Clark James'), ('Mrs.Rignald')
SELECT * FROM FullNameTest
Rules
1. Treat entries
(Mrs,Mr,Miss
etc)
as
Titles
andi
gnore the dot (.) after
title
2.
When
we have title
and
a single name,
return
it
as
Title,
LastName
3.
When
we have title
andtwo
names return
it
as
Title,
FirstName
and
LastName
4.
When
we have title
and
three names,
return
Title,
FirstName
and
treat the rest
as
LastName
5.
When
we have
no
title,
reurn data
as
FirstName,L
astName
 6. No
function
required.
So we can get values like below:
Title FirstName LastName
Mr Hog Finn Gad
Null Grace Bruce
Dr Null Paul
Master Clark James
Mrs Null Rignald
Thank you
Zionlite

Answer 1

Splitting a string based on a delimiter has been discussed many times - searching the internet will find many examples and discussions. With a splitter function you can parse apart all of the individual elements - with the set of elements you can then apply
your logic. 
Next:
1. Treat entries
(Mrs,Mr,Miss etc) as Titles andi gnore the dot (.) after title
This is not a "rule".  You will need to identify the entire set of values you wish to consider titles.  "etc." is not something you can write logic with (nor test for).
Next:
6. No function required.
Perhaps you meant to say "cannot use a user-defined function"?  And in what context?  Is the use of a splitter function not possible?  Regardless, if you have very specific implementation requirements, you should identify the reason
behind them.  Given your level of experience, it may be that you have a fundamental misunderstanding or a false assumption.  Even if there are valid reasons for such, it is better to be aware of the implications of this path.
Next, your sample data should be concerning to you, since it is to me.  You have examples where there is no space between elements (e.g., Dr.Paul).  Perhaps there is an unspoken first cleansing step, which is to replace periods with a
single space?  In this case, part of rule 1 is incorrect since the period (if found) is significant and must be replaced with the appropriate delimiter (single space).    
Next, there are unspoken assumptions in your data and in your logic.  It appears that your data always comes in a specific order (though elements are optional).  Title, if provided, is first. The last element will always be the last name. 
There will always be at least 2 elements. And so forth. 
Lastly, this is logic that should be applied when the data is inserted or updated.  Do NOT expect to apply this on a query-by-query basis and expect efficient performance. 
I suggest you try developing your solution in a step-wise fashion.  First, go find a splitter function.  Then write a query that will apply this function to your string column.  Once you get that working, you can then start writing your logic.