640 results found

1. Make the "Enclose identifiers within square brackets [ ]" option persist

   Currently in Visual Studio the option to "Enclose identifiers within square brackets []" option will be set to true on startup requiring a user to turn it off every time they load Visual Studio.

   This option when set to false should remain that way even after a restart of Visual Studio the same way it does in SSMS.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add NULL to JOIN suggestions

   When joining two tables, you today get the option to join on known references or identical column names.

   What I would like to see is an extra join option in the suggestions, if both the columns are NULLable:

   SELECT * FROM table1
   INNER JOIN table2 ON (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

   The above example might seem like rubbish at first! But sometimes when you have composite keys, one of the columns in the key might very well be a NULLable value.

   So a more valid example would be:

   SELECT * FROM table1
   INNER JOIN table2 ON table2.comp1 = table1.comp1 AND (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

   When joining two tables, you today get the option to join on known references or identical column names.

   What I would like to see is an extra join option in the suggestions, if both the columns are NULLable:

   SELECT * FROM table1
   INNER JOIN table2 ON (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

   The above example might seem like rubbish at first! But sometimes when you have composite keys, one of the columns in the key might very well be a NULLable value.

   So a more valid example would be:

   SELECT * FROM table1
   INNER JOIN… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Subquery Column Validation Hint

   There's an obscure coding bug that I've seen multiple times in my 20 years of working with SQL Server, and it can be particularly difficult to spot as it doesn't cause a syntax error, yet the havoc it wreaks can be widespread. Consider the following scenario with two tables; they are similar but have differing column names. Now say I want to insert records from StagingTable into FinalTable, but only if they don't already exist there. Yes, there are other ways to handle this like Merge, Left Outer Join etc., but this is still commonly used and you will no doubt see it in the wild.

   DROP TABLE IF EXISTS dbo.StagingTable;
   CREATE TABLE dbo.StagingTable (Col1 INT, Col2 INT);
   INSERT dbo.StagingTable (Col1, Col2)
   VALUES (1,1), (2,2), (3,3), (4,4);

   DROP TABLE IF EXISTS dbo.FinalTable;
   CREATE TABLE dbo.FinalTable (Int1 INT, Int2 INT);
   INSERT dbo.FinalTable (Int1, Int2)
   VALUES (1,1), (2,2), (3,3);

   --Insert new rows from stagingtable into FinalTable if rows don't already exists there.
   --In this scenario, we should insert 1 row with values (4,4)
   INSERT dbo.FinalTable (Int1, Int2)
   SELECT Col1, Col2
   FROM dbo.StagingTable stg
   WHERE NOT EXISTS (SELECT * FROM dbo.FinalTable WHERE Col1 = stg.Col1)

   --FinalTable still only has three rows, and (4,4) isn't among them.
   SELECT * FROM dbo.FinalTable

   Now, before reading on, run the script above and see if you can figure out why the new row isn't being added.

   In the NOT EXISTS subquery (anti-semi-join), the coder assumed that Col1 exists in FinalTable, but that isn't the case. One might expect this would be cause for a syntax error, but in reality, Col1 DOES exist in the scope of the overall statement, so SQL Server assumes you know what you are doing and executes the query without error, but also without inserting any new data. It's the same as a subquery having a predicate of WHERE 1=1 which of course isn't the desired behavior. The simplest way to avoid this is to ensure that all columns are qualified with table name or alias. When qualified, SQL quickly notices that something is wrong, and points out the error either at parse-time or run-time.

   My suggestion is for SQL Prompt to detect subqueries and call them out IF they use unqualified columns. I'm not suggesting a call-out of missing qualifications in ALL queries as it isn't always required, but by checking subqueries, it might go a long way to preventing this in the future.

   The simple fix to the insert statement above is of course the following:

   INSERT dbo.FinalTable (Int1, Int2)
   SELECT Col1, Col2
   FROM dbo.StagingTable stg
   WHERE NOT EXISTS (SELECT * FROM dbo.FinalTable ft WHERE ft.Int1 = stg.Col1)

   There's an obscure coding bug that I've seen multiple times in my 20 years of working with SQL Server, and it can be particularly difficult to spot as it doesn't cause a syntax error, yet the havoc it wreaks can be widespread. Consider the following scenario with two tables; they are similar but have differing column names. Now say I want to insert records from StagingTable into FinalTable, but only if they don't already exist there. Yes, there are other ways to handle this like Merge, Left Outer Join etc., but this is still commonly used and you will no… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Code Analysis  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Aliases Postfixes to ignore

   Similar to the "Prefixes to ignore" option in Options > Inserted code > Aliases, could we have a "Postfixes to ignore" option to allow use to set words at the end of a tablename to ignore when generating aliases.

   Currently I have to keep the custom aliases list up to date, whereas this would do that automatically.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Shortcut to switch equality statements

   It would be very convenient when going through legacy scripts to be able to hit a shortcut combination to switch the order of an equality statement, for example in a JOIN clause

   For example, with the cursor on "A.ID = User.AccountID":

   SELECT U.Username
   FROM Account AS A
   INNER JOIN Users AS U ON A.ID = U.AccountID AND U.Active = 1
   WHERE A.ID = @AccountID AND U.ID = @UserID

   Becomes
   SELECT U.Username
   FROM Account AS A
   INNER JOIN Users AS U ON U.AccountID = A.ID AND U.Active = 1 --note, only clause where cursor is is switched.
   WHERE A.ID = @AccountID AND U.ID = @UserID

   This would then compliment the casing/qualifying/wildcards/semicolons shortcuts you already have which massively speed up sorting out old queries.

   It would be very convenient when going through legacy scripts to be able to hit a shortcut combination to switch the order of an equality statement, for example in a JOIN clause

   For example, with the cursor on "A.ID = User.AccountID":

   SELECT U.Username
   FROM Account AS A
   INNER JOIN Users AS U ON A.ID = U.AccountID AND U.Active = 1
   WHERE A.ID = @AccountID AND U.ID = @UserID

   Becomes
   SELECT U.Username
   FROM Account AS A
   INNER JOIN Users AS U ON U.AccountID = A.ID AND U.Active = 1 --note, only clause where cursor is is switched.
   WHERE A.ID = @AccountID… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  User interface  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Custom Aliases - Ability to Alphabetize by table name

   Custom Aliases - Ability to Alphabetize by table name

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  User interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Custom Aliases - Ability to Create a List to Import

   Custom Aliases - Ability to create the list and import without having to use the SQL Prompt - Options-New... Interface. Reasons: Speed and to alphabetize.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add support for LEAST and GREATEST

   Please add support for the new SQL functions LEAST and GREATEST. Currently only available on Azure DB.
   Information (can't find official Microsoft documentation): https://www.linkedin.com/feed/update/urn:li:activity:6737816854498291712/

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Intellisense  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Support for MS Dataverse / CDS

   Add support so SQL Prompt will work in SSMS when connected to MS Dataverse / CDS (Common Data Service - Dynamics really).

   Right now, it fails since the (meta)data exposed probably isn't quite as complete as on a "full-scale" SQL Server database

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Platform Support  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. New code analysis rule: predicate data type agreement

    Please create a rule that detects when the data type of input parameters, local variables, and/or expressions do not match the data type of the column in a predicate.

    For example, if we have

    a Person table, with column LastName varchar(60) NOT NULL, and

    in the body of a stored procedure which has an input parameter defined as @LastName nvarchar(100)... and a predicate like WHERE Person.LastName = @LastName [join, apply, correlation, and functions also need this]

    It would be wonderful - save me massive amounts of time - if SQLPrompt could flag this and help reduce implicit conversions.

    Thank you!

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. [RESOLVED] Allow adding screenshots while posting an idea

    Please allow adding images/screenshots while posting an idea. Sometimes it gives a better understanding of the requirement.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. I would like to be able to re-name a tab without actually saving it off as a sql file.

    I would like to rename tabs without having to save them as a .sql file to the filesystem. I run with alot of tabs all the time and it gets very difficult if you don't name them to find a tab that has floated into the dreaded drop down arrow. Once its there I have to walk through the whole contents of the drop down list of query windows to find the one I want. With a simple rename of the tab that could be managed by the solution file. I would be able to label them and track them down much easier.

    I would like to rename tabs without having to save them as a .sql file to the filesystem. I run with alot of tabs all the time and it gets very difficult if you don't name them to find a tab that has floated into the dreaded drop down arrow. Once its there I have to walk through the whole contents of the drop down list of query windows to find the one I want. With a simple rename of the tab that could be managed by the solution file. I would be able to label them and track them… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  User interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Multi Line Comment shortcut

    Add /* / multi line comment shortcut for highlighted code in text editor. See SSMSBoost pro for example CTRL+.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Fix closing quote for 'N' strings

    When typing a string preceded with 'N' (like N'string value'), when you type the closing quote it gets doubled. Hard to explain, but easy to reproduce. Just type these two statements into SSMS to see the difference:

    SELECT 'Bill' As FirstName
    SELECT N'Bill' As FirstName

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Quick Edit For Table Row Data In Query Result Grid

    Scenario:
    If I run any select query where filed1=value1 etc, and it shows one or more rows in the grid below.
    Now I identify a required change and want to update that column value in a particular row.

    Current Process:
    One option is to write an update query and change the column value.

    The second option is to right-click on the table and go to edit but again it only shows a limited number of rows at a time.

    Requirement:
    Option1: Allow right click on result grid and give the option to script the selected row/columns(s) as edit query.

    Option2: Allow right click on result grid and give the option to directly open edit for that table/row

    Option3: Allow direct edit of the row in result grid or in an editable popup window.

    Scenario:
    If I run any select query where filed1=value1 etc, and it shows one or more rows in the grid below.
    Now I identify a required change and want to update that column value in a particular row.

    Current Process:
    One option is to write an update query and change the column value.

    The second option is to right-click on the table and go to edit but again it only shows a limited number of rows at a time.

    Requirement:
    Option1: Allow right click on result grid and give the option to script the selected row/columns(s) as edit query.

    Option2:… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Copy results as Markdown Table

    When right-clicking in the results tab, SQL Prompt should offer the posibility to copy the results as a table with markdown formatting (for Stack Overflow / Stack Exchange network). See https://meta.stackexchange.com/questions/356997/feature-preview-table-support for the syntax.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  User interface  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Cloud Backup of all SQL Prompt Settings

    Hi guys,

    SQL Prompt is great. What is less great is migrating from one computer to another (or rebuilding your machine / VM / whatever).

    It would be super useful if we could have a cloud backup of all SQL Prompt settings, styles, and snippets which can be associated with our licence account.

    When we do an install on a new machine, we'd then be given the option to restore settings from the cloud.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Tab History - Closed tabs

    It would be nice to have an ability to use either CTRL + click and SHIFT + click combos or to have check boxes there in order to select multiple closed scripts for a removal from Tab History instead of repeatedly hitting Remove context menu choice. It should save developer's time. Check boxes would be even better implementation choice, because that way you can apply context menu choice to a selection of scripts. Yay!
    Thanks!

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Tab history  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Option / Action to remove square brackets from types

    I prefer types without square brackets ( INT vs [INT], for example).

    If using square brackets for identifiers in the format options, there is no quick way to remove these.

    My work-around is -
    1. Apply Format Style option "Add/remove brackets + Remove Unnecessary brackets"
    2. Format the block of code
    3. Apply format Style option "Add/remove brackets + Add brackets to all identifiers"
    4. Format the block of code
    5. restore format Style option to original choice

    It would be nice to have a single action to do this, or to have a separate option in format styles to "Remove square brackets from types"

    I prefer types without square brackets ( INT vs [INT], for example).

    If using square brackets for identifiers in the format options, there is no quick way to remove these.

    My work-around is -
    1. Apply Format Style option "Add/remove brackets + Remove Unnecessary brackets"
    2. Format the block of code
    3. Apply format Style option "Add/remove brackets + Add brackets to all identifiers"
    4. Format the block of code
    5. restore format Style option to original choice

    It would be nice to have a single action to do this, or to have a separate option in format styles to… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Smart Rename should be smarter about changing schema &table name

    When renaming both the table and schema name, and a table already exists w/ the old table name but new schema name, Smart Rename errors because it does not detect this conflict and tries to first rename the table to the conflicting table name.
    
    e.g., renaming stage.dboTable1 to dbo_stage.Table1 (and stage.Table1 already exists):

    EXEC sp_rename N'[stage].[dboTable1]', N'Table1', N'OBJECT'
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    ALTER SCHEMA [dbo_stage] TRANSFER [stage].[Table1]
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    

    would work if script instead did this:

    ALTER SCHEMA [dbo_stage] TRANSFER [stage].[dboTable1]
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    EXEC sp_rename N'[dbo_stage].[dboTable1]', N'Table1', N'OBJECT'
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    

    Note: your editor control apparently interprets special characters as HTML

    When renaming both the table and schema name, and a table already exists w/ the old table name but new schema name, Smart Rename errors because it does not detect this conflict and tries to first rename the table to the conflicting table name.
    
    e.g., renaming stage.dboTable1 to dbo_stage.Table1 (and stage.Table1 already exists):

    EXEC sp_rename N'[stage].[dboTable1]', N'Table1', N'OBJECT'
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    ALTER SCHEMA [dbo_stage] TRANSFER [stage].[Table1]
    GO
    IF @@ERROR <> 0 SET NOEXEC ON
    GO
    

    would work if script instead did this:

    ALTER SCHEMA [dbo_stage] TRANSFER [stage].[dboTable1]
    GO
    IF @@ERROR <> 0 SET NOEXEC

    … more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Smart rename  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close