What SQL is
SQL here means the statements that move a table into a database: INSERT INTO with a VALUES list, and optionally the CREATE TABLE that defines the columns.
Anyone seeding a database, moving a spreadsheet into an application, or writing a migration.
What TSV is
TSV is CSV with tabs instead of commas. Because tabs almost never appear inside a value, quoting is rarely needed and the files are easier to read by eye.
Bioinformatics, log processing, and anyone who has copied a block of cells out of a spreadsheet: the clipboard format is TSV.
What changes when you convert SQL to TSV
Column names come from the INSERT column list, or from a CREATE TABLE if one is present. Quoted strings are unquoted, doubled quotes are collapsed, and NULL becomes an empty cell.
Pick TSV over CSV when your values contain commas. Pasting the result straight into a spreadsheet fills the cells correctly with no import dialog.
What carries over from SQL to TSV
SQL records 4 things about a table that TSV has no way to hold.
SQL distinguishes a number from the text of a number; TSV does not, so every value arrives as text and has to be re-parsed by whatever reads it next.
An empty cell and a missing one are the same thing in TSV, so a null and an empty string in the SQL both come out blank and can no longer be told apart.
A line break inside a cell ends the row in TSV, so line breaks are replaced rather than carried through.
TSV has no separate idea of a header, so the column names become an ordinary first row and nothing in the file marks them as different from the data.
The identifier 007 comes out of the TSV as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a TSV file goes wrong.
The quotes around Jonah "Jo" Pryce are doubled, which is how the delimited formats escape a quote in the TSV.