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 reStructuredText is
reStructuredText simple tables underline the header with equals signs and align columns with spaces.
Python documentation, Sphinx projects and anything on Read the Docs.
What changes when you convert SQL to reStructuredText
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.
The equals-sign rule under the header is what tells Sphinx the first row is a header. Without it the table renders as data with no heading.
What carries over from SQL to reStructuredText
SQL records 3 things about a table that reStructuredText has no way to hold.
SQL distinguishes a number from the text of a number; reStructuredText 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 reStructuredText, so a null and an empty string in the SQL both come out blank and can no longer be told apart.
SQL can be read one record at a time. reStructuredText has to be complete before it means anything, so the whole table is held in memory while it is written and a file that gets cut off part way through is not partly usable - it is unusable.
The identifier 007 comes out of the reStructuredText 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 reStructuredText file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the reStructuredText.