Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Hekaton - Origin Expand / Collapse
Author
Message
Posted Wednesday, April 30, 2014 1:05 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:14 PM
Points: 44, Visits: 113
Hi all,

Someone knows the origin of the name "hekaton" because in previous editions the name was based mountains.

Thanks.

Post #1566567
Posted Wednesday, April 30, 2014 1:09 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 12:12 AM
Points: 1,219, Visits: 3,555
Maybe this might help
Post #1566569
Posted Wednesday, April 30, 2014 1:57 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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, εκατόν 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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1566599
Posted Wednesday, April 30, 2014 2:08 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 12:12 AM
Points: 1,219, Visits: 3,555
On a mediocre laptop, 10000000 rows returned in 145 ms and 100000 inserts in 75 ms, I think version 1 is promising.
Post #1566603
Posted Wednesday, April 30, 2014 2:17 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1566604
Posted Wednesday, April 30, 2014 3:18 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:14 PM
Points: 44, Visits: 113
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.

Post #1566617
Posted Thursday, May 1, 2014 7:21 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1566702
Posted Thursday, May 1, 2014 9:49 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:14 PM
Points: 44, Visits: 113
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.

Post #1566760
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse