TSQL/MS SQL Server statements/syntax not supported. #1563

Activity

1. manticore-projects

   added

   improvement

   on Jun 11, 2022
2. manticore-projects

   self-assigned this

   on Jun 11, 2022
3. wumpz commented on Jun 28, 2022

   

   wumpz

   on Jun 28, 2022

   Member

   More actions

   Did you investigate this issue further?
4. minleejae commented on Sep 21, 2026

   

   minleejae

   on Sep 21, 2026

   Contributor

   More actions

   @manticore-projects I revisited the two Sakila scripts linked in this issue and verified them against current master (8e2d660), using Dialect.SQLSERVER with unsupported-statement fallback disabled.

   Both scripts parse successfully without modifying or preprocessing the input:

   Input	Parsed statements	Result
   Schema script	70	Pass
   Current insert-data script	46,326	Pass
   Insert-data script as it existed when this issue was opened	46,326	Pass

   I also deparsed and reparsed each complete script and checked that statement types, counts, and rendered SQL were preserved. No UnsupportedStatement nodes were produced.

   The relevant syntax gaps were addressed by:

   • Support dialect-specific CREATE INDEX definitions #2586: SQL Server index definitions
   • Accept SQL Server CREATE TABLE trailing commas with shared element parsing #2603: trailing commas in SQL Server CREATE TABLE
   • Support SQL Server SET IDENTITY_INSERT with a structured table target #2605: SET IDENTITY_INSERT

   All three fixes are included in the jsqlparser-5.4 tag; the verification above was run on current master.

   Since the original reproductions now pass, would you agree that this issue can be closed as resolved?
5. manticore-projects commented on Sep 21, 2026

   

   manticore-projects

   on Sep 21, 2026

   ContributorAuthor

   More actions

   Absolutely, great job!
   We need to mention this on the Website as well!
6. manticore-projects

   closed this as completedon Sep 21, 2026