Revision as of 12:05, 25 March 2019 edit Meno25 (talk \| contribs) Autopatrolled, Administrators 216,392 edits Assessment: Databases: class=List; Microsoft: class=List (assisted) ← Previous edit		Revision as of 23:40, 11 April 2019 edit undo Argenis (talk \| contribs) 9 edits →Code Names Next edit →
Line 19: == Code Names == Perhaps we need a separate section on code names. Or is it too trivial? Two contentious code names are Hekaton and Helsinki. Although they do not directly map to a specific SQL Server release, they refer to the largest feature waiting to get integrated into vNext, and typically were referred to by that name, especially in early product life-cycle. Another code name was Acadia which was the version after SQL 2003 (which slipped to 2005). [[User:Paul.wehland\|Paul.wehland]] ([[User talk:Paul.wehland\|talk]]) 20:26, 16 February 2018 (UTC) I updated the codenames today with the right ones :) Hekaton indeed wasn't the codename for SQL2014. That's a myth. Internally that release was always known as SQL14. SQL15 became SQL16, and then Helsinki hit the radar. However unlike Hekaton, Helsinki referred to the overall release, not just SQL Server on Linux. [[User:Argenis\|Argenis]] ([[User talk:Argenis\|talk]]) 16:28, 11 April 2019 (PST)

Talk:History of Microsoft SQL Server: Difference between revisions