Post reply

Query returns wrong data with in-memory table and clustered column store index

  • October 29, 2019 at 9:29 am

    #3692621

    Hi,

    i have a problem with using in-memory tables in conjunction with clustered column store index.

    Although i can't believe this, but i think I found a bug in SQL Server 2016/2017/Azure Database.

    I posted my problem already on StackOverflow (I hope it is OK to cross link here).

    I attached a working Repo as a T-SQL script (SQL CMD MODE).

    After running the script you should see following wrong results:

    Wrong results

    After creating e.g. an additional index on table [Attribute]

    CREATE INDEX [IX_Attribute_Nested_Set] ON [dbo].[Attribute] ([LeftExtent], [RightExtent])

    Correct results

    Can anyone confirm this strange results!

    As I said before it look like a bug for me!

    Regards,

    Daniel

     

    Attachments:
    You must be logged in to view attached files.

  • October 30, 2019 at 10:10 am

    #3693017

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • November 20, 2019 at 8:09 am

    #3699115

    Is there really no one who can reproduce my issue !?!?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply