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

Project Hekaton Expand / Collapse
Author
Message
Posted Tuesday, November 5, 2013 8:09 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:16 PM
Points: 31,284, Visits: 15,748
Comments posted to this topic are about the item Project Hekaton






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1511700
Posted Wednesday, November 6, 2013 4:58 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:18 AM
Points: 5,756, Visits: 3,675
Microsoft is continuing to benefit from its open attitude towards research, development and release. Some functionality, products and/or features get dropped along the way but this has always been the case. I can remember that Windows 2000 Advanced Server was due to have a feature called IMDB (In Memory DataBase) which was in the betas but was dropped in the final release. There are always complaints when something is dropped as there is always someone who uses it but there is always the caveat that anything can be dropped at any time (or sometimes support cycles are defined for released products such as editions of Windows or SQL Server).

It will be interesting how much use that this feature will get in production systems.

As a developer I have little interest in this feature.
As a software engineer I have a need to understand what this feature offers.
As a software architect this could be a key feature that alters a proposed solution.


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1511808
Posted Wednesday, November 6, 2013 6:02 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 13, 2014 3:00 PM
Points: 12, Visits: 24
Everything old is new again. Back in the day, I packed a machine with RAM, created a VDisk and assigned tempdb to the VDisk. The machine's performance jumped!
I tried putting some of the smaller lookup tables there. But that that made rebooting the server a pain. Now they are putting ALL the tables into RAM. How long does a reboot take?




Post #1511838
Posted Wednesday, November 6, 2013 8:50 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, June 25, 2014 9:06 AM
Points: 125, Visits: 132
I saw Dr DeWitt's keynote at Summit 13 and was impressed by how he explained Hekaton in a way that made it easy to understand for an earthling like me.

But then I tried to figure out how I would use it in my work, and can't find a good application for it. But we won't be using this type of feature anytime soon. Most of the OLTP systems we have are still in a mainframe environment. (Yea, we're a little behind the times :).
Post #1511913
Posted Wednesday, November 6, 2013 10:00 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, November 20, 2014 12:26 PM
Points: 726, Visits: 186
Recently I looked at a implementing this feature as I have an environment that is a perfect fit. However because of limitations against xml, lob data as well as FKs I don't seeing this being deployed. I love the idea though.


Russ
Post #1511934
Posted Wednesday, November 6, 2013 10:28 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 2:50 PM
Points: 1,937, Visits: 2,107
I've seen a number of people who compare the Hekaton features to the old school SQL Server 2000 and earlier OLTP methodology of readers block writers and writers block readers, but I've yet to find a good comparison of Hekaton to the more modern (2005 and up) OLTP methodology of using row versioning isolation levels for concurrency. Also given the restrictions on what things you can't do with them,
http://msdn.microsoft.com/en-us/library/dn246937(v=sql.120).aspx, and that you need memory tables to use compiled stored procedures, I think this is a real fringe feature, and few real world systems will be able to take advantage of them.
Post #1511945
Posted Wednesday, November 6, 2013 10:30 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 8:49 PM
Points: 17,967, Visits: 15,979
swwg69 (11/6/2013)
Everything old is new again. Back in the day, I packed a machine with RAM, created a VDisk and assigned tempdb to the VDisk. The machine's performance jumped!
I tried putting some of the smaller lookup tables there. But that that made rebooting the server a pain. Now they are putting ALL the tables into RAM. How long does a reboot take?






I imagine most databases out there would benefit very little if any from this. But there are some cases that I think I could make some customers a little happier with the performance gain.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1511950
Posted Wednesday, November 6, 2013 6:48 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 7:42 PM
Points: 635, Visits: 2,215
I could see this feature to be worth something to someone. But before I would use it I'd find someone to build me a SAN RAID unit based on Solid State Disks with a disk fail system.

I have been burned by one too many UPS/Generator/Switch failure in the past to trust data to plain old volatile RAM.

This is a Mongo DB Is Web Scale solution. As an eBay/Amazon/Google use yes. But they have the money to do triple redundancy failover solutions. Most of us aren't at that scale.




----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1512053
Posted Wednesday, November 6, 2013 8:48 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 11:59 AM
Points: 594, Visits: 933
As far as dealing with RAM and its inherent volatility Hekaton adheres to the durable principal of A.C.I.D., so once committed the data isn't lost. With the limitations and the unknown issues (corruption, impact on RAM, etc) I think I will have to wait until the next release. I do believe that it could have many uses and will start playing with it, just not in production.



Microsoft Certified Master - SQL Server 2008
Follow me on twitter: @keith_tate

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1512072
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse