Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Thanks Jovan, it was due to compatibility level. It works with 130.
    – Iva
    Commented Apr 7, 2016 at 9:08
  • 2
    Now My Error is "Valid values of the database compatibility level are 90, 100, or 110". Commented Sep 28, 2017 at 5:49
  • Are you talking about Azure SQL Database or some SQL Server version? Azure SQL should have all compatibility levels available.
    – Jovan MSFT
    Commented Sep 29, 2017 at 12:25
  • For extra info, read: asptricks.net/2017/07/invalid-object-name-openjson-in-sql.html Commented Feb 21, 2018 at 15:11
  • 2
    @DurgeshPandey If you run SELECT @@VERSION you will see you are running SQL Server 2012 (compatibility level 110) so that error message is telling you that you can't change to a compatibility level for a version of SQL Server that is newer than what you have, i.e. SQL Server 2016 (compatibility level 130).
    – Davos
    Commented Mar 6, 2018 at 0:53