NAV2015 - In-memory tables possible?

TomigsTomigs Member Posts: 86
edited 2015-02-03 in NAV Three Tier
Hi experts,

We have heard about the new capacities in using in-memory technology for tables in SQL Server 2014, that apparently can improve significantly the performance of the database (http://www.eweek.com/database/slideshow ... ology.html)

My question is if you know if NAV2015 can benefit from this feature.

I have looked at a very useful topic at Kriki's blog (http://mibuso.com/blogs/kriki/ - "SQL Server 2014 and NAV"). If I have understood well tables should be created in SQL with certain properties, that should also be present in NAV2015 developement environment (or maybe change the table properties directly in SQL). Furthermore, in-memory tables are only available for SQL Enterprise edition. So my guess is that right now NAV2015 won't benefit from it but I'm not sure and I wonder if any of you have studied this topic more carefully and know about it.

Thank you very much,

Tomas.

Answers

  • bbrownbbrown Member Posts: 3,268
    Being an "Enterprise Only" feature, I have serious doubt that Microsoft will ever invest adequate time to test and support such a feature with NAV. Also my understanding is it does not work with some of the SQL features that NAV 2015 uses. Such as MARS.
    There are no bugs - only undocumented features.
  • ara3nara3n Member Posts: 9,256
    Hello Tomas

    Currently they are not possible with standard NAV development environment.
    There are a couple things that prevent this.

    ALTER TABLE, sp_rename, and adding and removing an index is not supported for memory-optimized tables.

    Time Stamp is not supported either.


    They are the perfect solution for SIFT for enterprise SQL version. Currently VSIFT (indexed views) a huge problem for Locking.

    MS should separate SIFT from indexes. Add a new property called VSIFT and allow a user to group by and SUM. Then store the data an maintain them in the In Memory tables because it Includes in the new architecture a lock-less concurrency model.

    They could use it for certain tables like no series line.

    Or even a table that keeps track of Entry No for all the subledger.

    So non enterprise customer keep VSIFT and for enterprise use memory table. You'll have to ask MS for an answer.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • TomigsTomigs Member Posts: 86
    Ok, thank you very much both for your answer.
Sign In or Register to comment.