Timeline for OPENJSON does not work in SQL Server?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2019 at 16:43 | comment | added | Rinku Choudhary | i have face the error "Valid values of the database compatibility level are 100, 110, or 120" and i have ssms 2018 | |
| Mar 6, 2018 at 0:53 | comment | added | Davos |
@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).
|
|
| Feb 21, 2018 at 15:11 | comment | added | Jacob van Lingen | For extra info, read: asptricks.net/2017/07/invalid-object-name-openjson-in-sql.html | |
| Sep 29, 2017 at 12:25 | comment | added | Jovan MSFT | Are you talking about Azure SQL Database or some SQL Server version? Azure SQL should have all compatibility levels available. | |
| Sep 28, 2017 at 5:49 | comment | added | Durgesh Pandey | Now My Error is "Valid values of the database compatibility level are 90, 100, or 110". | |
| Apr 11, 2016 at 12:28 | history | edited | Jovan MSFT | CC BY-SA 3.0 |
added 359 characters in body
|
| Apr 8, 2016 at 12:44 | history | edited | Jovan MSFT | CC BY-SA 3.0 |
added 21 characters in body
|
| Apr 7, 2016 at 18:02 | history | edited | Jovan MSFT | CC BY-SA 3.0 |
Added a note that in Azure SQL Database default level is still 120.
|
| Apr 7, 2016 at 9:08 | vote | accept | Iva | ||
| Apr 7, 2016 at 9:08 | comment | added | Iva | Thanks Jovan, it was due to compatibility level. It works with 130. | |
| Apr 7, 2016 at 9:00 | history | answered | Jovan MSFT | CC BY-SA 3.0 |