Talk:NonStop SQL

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.

Databases (inactive)

This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles

Jim Gray, who worked on NonStop SQL and who came to Tandem from IBM's System R project, told me:

"There was no direct connection between NonStop SQL and Ingres. Enform (a report writer that preceeded NonStop SQL) was used some of the Ingres syntax. Jerry Held was busy with Rainbow [a different project within Tandem] (as was Carol Youseffi). Neither worked on NonStop SQL at the start. When Rainbow was canceled, I think Carol joined the SQL optimizer group."

Perhaps you were influenced by the (incorrect) statement in http://now.cs.berkeley.edu/~brewer/cs262/SystemR.html ?

Paul McJones http://www.mcjones.org/System_R/

Current Versions

"The latest version of the product is SQL/MX 3.0 which was released in February 2011." This statement is no longer accurate - HP has released: - 3.1 in Aug 2011 - 3.2 in Aug 2012 - 3.2.1 in Feb 2013 — Preceding unsigned comment added by Mgdupont (talk • contribs) 20:36, 4 February 2014 (UTC)[reply]

"Nonstop sql" listed at Redirects for discussion

An editor has identified a potential problem with the redirect Nonstop sql and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 January 2#Nonstop sql until a consensus is reached, and readers of this page are welcome to contribute to the discussion. Closeapple (talk) 03:08, 2 January 2022 (UTC)[reply]