SQL started as SEQUEL, then a trademark issue took the vowels
The original IBM paper and Don Chamberlin’s later history explain the name without requiring a winner in the pronunciation argument.

SQL began with enough vowels to settle at least one part of the pronunciation argument. Its original name was SEQUEL, short for Structured English Query Language. A trademark issue later cut the name to SQL. The database kept its tables; the name lost a couple of columns.
IBM Research’s record of the original paper dates it to May 1, 1974, and names Donald Chamberlin and Raymond Boyce as the authors. The title and abstract use SEQUEL. That gives the origin story something more useful than an argument remembered from an office kitchen: a contemporary publication with the name printed on it.
The abstract describes operations on tabular structures and keyword English templates that can be composed into more complex queries. The intended audience includes professional programmers and people using a database less frequently. The designers were trying to make the language usable without requiring the user to work directly with bound variables and quantifiers.
That intention is more specific than saying the language made databases effortless. A template resembling English can reduce one obstacle while leaving the user responsible for what a query means. Asking for a set of rows still requires knowing which rows belong in the answer. A friendly menu cannot decide what somebody meant to order.
In his later encyclopedia entry, Chamberlin writes that “because of a trademark issue” the name changed in 1977. That account establishes the reason at that level. It does not identify the trademark holder in the quoted passage, and it does not require inventing a courtroom scene to make the missing vowels interesting.
The entry also describes the language evolving through experience with the System R project. A fuller account appeared in 1976, covering more manipulation and administration facilities. The name change therefore happened during an ongoing design history, rather than creating a wholly different language overnight. Renaming the cupboard does not replace everything inside it.
Chamberlin records that the first commercial SQL product was Oracle, released by Relational Software, Inc. in 1979. IBM’s SQL/Data System followed in 1981, then DB2 in 1983. The research origin and first commercial release belong to different organizations, which is easy to miss when the origin story is reduced to one company and one date.
For a team writing documentation, the practical payoff is modest. Using SQL consistently as the language name avoids turning a technical document into a pronunciation test. When historical material says SEQUEL, retaining that original spelling makes the chronology clearer. Readers can follow the published record without being assigned a preferred way to say the modern abbreviation.
The paper trail confirms which name came first and why it shortened. It does not make every present-day pronunciation into an engineering error. There is still room for people to say the letters aloud, while someone saying “sequel” can point to a name the language really had before the trademark problem arrived.
Chamberlin dates the shortening to 1977.