locked
SQL 2014 In-Memory Hash Index Necessary? RRS feed

  • Question

  • My question is regarding the Hash Index. Is it necessary to create a Hash Index on a memory optimized table? If I don't create one, and just create a regular nonclustered index, do I have to provide a bucket count on this?

    Thursday, October 20, 2016 4:14 PM

Answers

  • No need for a hash index. You need at least one index, but it can be a "regular" (BW-tree) index. Such index do not have a bucket count, only hash indexes has bucket counts.

    Tibor Karaszi, SQL Server MVP (Web Blog)

    • Marked as answer by Diango Thursday, October 20, 2016 6:46 PM
    Thursday, October 20, 2016 5:37 PM

All replies

  • No need for a hash index. You need at least one index, but it can be a "regular" (BW-tree) index. Such index do not have a bucket count, only hash indexes has bucket counts.

    Tibor Karaszi, SQL Server MVP (Web Blog)

    • Marked as answer by Diango Thursday, October 20, 2016 6:46 PM
    Thursday, October 20, 2016 5:37 PM
  • What Tibor said is correct, you don't have to have a hash index. But for example, loading data with only a hash index will be faster than loading data with a nonclustered index, assuming the bucket count is set correctly, and other best practices for loading data are observed.

    So the type of usage/data access would determine whether or not you would want to have a specific type of index. 


    Ned Otter MCSE Data Platform

    Thursday, October 20, 2016 6:21 PM
  • Ok that clears up my question, thank you both for the comments!
    Thursday, October 20, 2016 6:46 PM