ROW_NUMBER returning NULL in Visual Studio 2017 vs Visual Studio 2015


  • I take the same code which runs on Visual Studio 2015 and gives me meaningful, ordered numbers and I then run that on Visual Studio 2017, and I get all NULLs.  Very strange.  Looks like ROW_NUMBER is broken.  Can you confirm?

    @distinctProducts =
        SELECT ROW_NUMBER() OVER(ORDER BY MaterialId DESC) AS ProductId,
        FROM @distinctProductsY;

    In this case MaterialID is not null, and has meaningful numbers present for every row.  Can you tell me what the issue might be?


    Thursday, October 12, 2017 6:10 PM

All replies

  • Sorry for the inconvenience, I am forwarding this error to our team members. Are you still re-producing this error?


    Tuesday, December 5, 2017 11:57 AM
  • hi, can you please provide version of VS2015 and VS2017 you are using, as well as the Data Lake tool version? We need these info to re-pro the bug.



    Wednesday, December 6, 2017 3:05 AM