Thanks a lot for the beta launch of the MSSQL Server Plugin for Tabularis.
I am a daily MS SQL Server user from an analyst and DWH requirement engineering perspective. That means I am a heavy "reader," but I don't write structures or manage the server.
The MS SQL dialect-specific TOP() instead of LIMIT is currently not correctly implemented:
When I use right-click → generate SQL → SELECT [Fields]
(I use the German language version, so the naming might not be exact),
I get a query using LIMIT.
Furthermore, when I edit it or write a query myself with TOP, it still does not work and returns the following issue:
Error: SQL Server error 102: Incorrect syntax near '100'. [syntax error; severity 15; state 1; line 11]; SQL Server error 102: Incorrect syntax near 'OFFSET'. [syntax error; severity 15; state 1; line 11]; SQL Server error 153: Invalid usage of the option NEXT in the FETCH statement. [statement failure; severity 15; state 2; line 11]
Happy to use the plugin more intensively and provide more feedback, once the issue is resolved.
Thanks a lot for the beta launch of the MSSQL Server Plugin for Tabularis.
I am a daily MS SQL Server user from an analyst and DWH requirement engineering perspective. That means I am a heavy "reader," but I don't write structures or manage the server.
The MS SQL dialect-specific TOP() instead of LIMIT is currently not correctly implemented:
When I use right-click → generate SQL → SELECT [Fields]
(I use the German language version, so the naming might not be exact),
I get a query using LIMIT.
Furthermore, when I edit it or write a query myself with TOP, it still does not work and returns the following issue:
Error: SQL Server error 102: Incorrect syntax near '100'. [syntax error; severity 15; state 1; line 11]; SQL Server error 102: Incorrect syntax near 'OFFSET'. [syntax error; severity 15; state 1; line 11]; SQL Server error 153: Invalid usage of the option NEXT in the FETCH statement. [statement failure; severity 15; state 2; line 11]Happy to use the plugin more intensively and provide more feedback, once the issue is resolved.