Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

SQL Source Control need to recognize SQL 2016 code

Currently SQL Source Control is crashing when SQL 2016-specific code is used, for example:
DROP TABLE IF EXISTS #input;

It should recognize this code since SQL Server 2016 works with it.

14 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Dmitriy shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
started  ·  fiona.gazeley responded  · 

This is caused by the SQL Compare parser not understanding this syntax. The good news is the SQL Compare team are currently working on SQL Server 2016 parser support. Once this work is done and SQL Source Control is updated with the latest SQL Compare engine, I will update this request again.

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Brookover commented  ·   ·  Report

    while not crashing, it cannot parse the new query options such as min_grant_percent and max_grant_percent.

  • Nicholas Orlando commented  ·   ·  Report

    Found that JSON also crashes both SQL Source Control and DLM Automation.

    DECLARE @JSON NVARCHAR(MAX) = '[{"ID":1,"Name":"Test"}]';

    SELECT ID, Name
    FROM OPENJSON(@JSON)
    WITH (
    ID INT N'$.ID',
    Name VARCHAR(255) N'$.Name'
    );