>> I'm a newbie to T-SQL. <<
Please read any book on basic RDBMS. As Dykstra used to say to his students, "you're doing everything completely wrong."
CREATE TABLE Tests
(person_id INTEGER NOT NULL, ---wrong data type
name_change NVARCHAR (75), --- what does Null mean?
PRIMARY KEY (??));
By definition, not as some vague option, a table must have a key. But you published what are basically a bunch of punchcards with redundant data and no possibility of having a unique row. You really don't know what a key is! Even before we got to RDBMS, the goal of databases was to remove redundancy. Not increase it.
So not only are you doing it wrong, you don't know the syntax of the insert statement has a row constructor. Instead you're inserting one row at a time. Just the way we used to insert punchcards into a magnetic tape file in the 1960s. Here is direct translation of your punchcards into unusable poor SQL.
INSERT INTO Tests -- garbage code!
(1,'Mr Herby Spike'),
(1,'Mr Herby Spoke').
(2,'miss Anne had'),
(2,'miss Anne hadbreakfast'),
(2,'miss Anne hadlunch'),
(3,'miss Laurrel hadlunch'),
(3,'miss Laurrel hadbreakfast'),
(3,'miss Laurrel hadtea'),
(3,'miss Laurrel haddinner');
An identifier is usually shown by the postfix "_id" and it is by definition on a nominal scale. This means you can't use numerics for it because you don't do any calculations. But ignoring the DDL, there is a more fundamental problem. If you read Dr. Codd any book on RDBMS, you will see that columns are supposed to be scalar values, not concatenated strings. In SQL and other tiered architectures. Such display formatting is done in a presentation layer, and never in the database.
What you've got here, is not really help, but a bunch of proprietary kludges. Please stop what you're doing and catch up on your reading.
Please post DDL and follow ANSI/ISO standards when asking for help.