Skip to content

Settings and activity

8 results found

  1. 25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Nicholas Orlando supported this idea  · 
  2. 18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Nicholas Orlando shared this idea  · 
  3. 304 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    47 comments  ·  SQL Prompt  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Nicholas Orlando commented  · 

    SQL Prompt would be nice to have in SQL Operations Studio along with SQL Source Control and SQL Test. Could live without SQL Test since there are tSQLt procs to run the tests, but not without SQL Prompt and SQL Source Control.

    Nicholas Orlando supported this idea  · 
  4. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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.

    An error occurred while saving the comment
    Nicholas Orlando commented  · 

    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'
    );

    Nicholas Orlando supported this idea  · 
  5. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Nicholas Orlando supported this idea  · 
  6. 207 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Nicholas Orlando supported this idea  · 
  7. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Nicholas Orlando supported this idea  · 
  8. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Nicholas Orlando commented  · 

    Miss spelled swapping with sapping, but don't see a way to edit the idea.

    Nicholas Orlando shared this idea  ·