New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sql Server 2008 "Invalid usage of the option NEXT in the FETCH statement." #85
Comments
SQL Server 2008 might need a separate dialect. I don't have that version installed so I can't test it. What is the generated SQL? |
I searched for this issue and I found Sql Server 2008 does not support FETCH.
I worked around it using this :
|
I got same issue, I dont think it's because Sql Server 2008.
here's my code I'm using Dotnetcore 1.1 EDITNevermind, Looks like I have to add so if you want a pagination, those three functions are mandatory |
I encountered this error when running against an old SQL 2008 R2 server. I installed SQL Express 17 on my box and the error went away. |
If you encounter this problem with Azure SQL, just change the Compatibility Level of your database to 130 or higher. You can do this via script or SQL Server Management Studio by looking at the database properties->options. |
Currently looking at this but honestly we don't have the resources to maintain the tests for this old dinosaur. |
Hi,
I'm using SQL Server 2008 and querying using this
But I got an error
The text was updated successfully, but these errors were encountered: