April 30, 2014 at 1:05 pm
Hi all,
Someone knows the origin of the name "hekaton" because in previous editions the name was based mountains.
Thanks.
April 30, 2014 at 1:09 pm
April 30, 2014 at 1:57 pm
Previously the versions had code names named after locations. Hekaton isn't a version (SQL Server 2014 is a version), hekaton is a feature and the features often get their own code names (eg xVelocity).
The word is greek, e?at?? it means one hundred. The feature was so named because their goal was a 100x speedup. Haven't got their yet, but this is v1.
http://www.thefreedictionary.com/hundred-
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 30, 2014 at 2:08 pm
On a mediocre laptop, 10000000 rows returned in 145 ms and 100000 inserts in 75 ms, I think version 1 is promising.
😎
April 30, 2014 at 2:17 pm
And how long does it take to do that to a normal disk-based table?
I tested it out, with the load I could generate on a laptop I could not get a measurable performance difference between disk-based table and memory table. Which is to be expected, since it's aimed at very high volume inserts (thousands of small inserts a second) and small queries, not at queries returning millions of rows, which is more the job of Columnstore.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 30, 2014 at 3:18 pm
GilaMonster (4/30/2014)
Hekaton isn't a version (SQL Server 2014 is a version), hekaton is a feature and the features often get their own code names (eg xVelocity).[/url]
Nice Gail, but hekaton is the official codename of the edition as the name of the feature.
May 1, 2014 at 7:21 am
Alexandre Araujo (4/30/2014)
Nice Gail, but hekaton is the official codename of the edition as the name of the feature.
It's not. It's the code name of what became in-memory OLTP. SQL 2014 had no code name, other than SQL14 which is what it was called during development
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 1, 2014 at 9:49 am
You're absolutely right !! I've thought that link http://sqlserverbuilds.blogspot.com.br/ was correct, but in wikipedia the correct code name is SQL14.
Thank you Gail.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply