669 results found

1. Separate ALIAS Alignment - table vs. column

   Aligning based on column-alias makes for much better readability. When turned OFF, because some long-named table's alias pushes the TABLE-alias way to the right, all other table aliases follow it...into the NON-VISIBLE area (when using multiple vertical tabs).

   Please SEPARATE these into TWO options:
   . Align Column Aliases - on/off
   . Align Table Aliases - on/off

   THERE IS A BUG TO FIX HERE TOO: If a UDF is bounded by "--SQL Prompt formatting off/on" the TABLE ALIAS position REMAINS as if the UDF's alias was in it's SQL Prompt position, NOT where the excluded code has it! NASTY.

   You could also FIX the NON-ALIGNMENT of UPDATE...SET...Column lists...

   Thanks

   Aligning based on column-alias makes for much better readability. When turned OFF, because some long-named table's alias pushes the TABLE-alias way to the right, all other table aliases follow it...into the NON-VISIBLE area (when using multiple vertical tabs).

   Please SEPARATE these into TWO options:
   . Align Column Aliases - on/off
   . Align Table Aliases - on/off

   THERE IS A BUG TO FIX HERE TOO: If a UDF is bounded by "--SQL Prompt formatting off/on" the TABLE ALIAS position REMAINS as if the UDF's alias was in it's SQL Prompt position, NOT where the excluded code has it! NASTY.

   You could… more

   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  ·  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. Separate UDF Formating from Built-in in "Function Calls"

   We cannot treat UDF parameter listing/indentation in similar vein to Stored Procedure call formatting. All "Functions", be they UDF or built-in, are lumped into the same four RESTRICTIVE options on the "Function calls" page, and we have no "parentheses style" options for them.

   We need:
   1. Separation by type (UDF vs. Built-in).
   2. Global ==> Parentheses, to apply to UDFs, by our choice.

   Thanks.

   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  ·  Format SQL  ·  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

3. Tab history remove duplicates scripts

   Have the ability to delete duplicate scripts in the Tab History. Example I may open a stored procedure to look at it or modify then close and then it is stored in the Tab History as Closed. But then in a few days or so I open the same store procedure and do the same thing it is now in the Tab History also. I have made no changes to either day it is open then closed but, it's in the Tab History twice. Now think about this over a few months. That Tab History grows with duplicate scripts.

   15 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

4. Ability to make/see notes about servers

   It would be very handy if there was a way when you open a server in Object Explorer that it pops up with notes about that server. For instance, there is a job we have on EVERY server in our environment except one random server that no one hardly thinks about. But if that job is there, then it messes up things. It would be great if when anyone on our team who has redgate sql prompt opens that server they get a reminder that we add on there that says some special note (in this case “DO NOT ADD AP Job!!!”). It could even be stored in like the extended properties for the server and SQL Prompt just reads that first when it’s opened. An optional feature on top of that, would be anytime you open that server as a new query window. I’d say optional, because some people may not want to see that everytime. But that would help as well when people want to see notes, but they never use the GUI and just write out all their code.

   It would be very handy if there was a way when you open a server in Object Explorer that it pops up with notes about that server. For instance, there is a job we have on EVERY server in our environment except one random server that no one hardly thinks about. But if that job is there, then it messes up things. It would be great if when anyone on our team who has redgate sql prompt opens that server they get a reminder that we add on there that says some special note (in this case “DO NOT ADD… more

   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  ·  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. Do not auto complete literal strings

   Currently SQL Prompt displays suggestions for auto-completing literal strings. These are never valid suggestions so can this be turned off (or at least have an option to turn this off)?

   •  

   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  ·  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

6. Find invalid objects in multiple databases

   Please could you add an option to check for invalid objects in multiple databases and to be able to export the results in either a single file or 1 per database. It's a real pain doing 1 at a time and manually selecting the results to do a copy/paste.

   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  ·  Find invalid objects  ·  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. Have Formal SQL Actions be included in the formatting style file.

   Have Formal SQL Actions be included in the formatting style file. This way when a team shared a standard we do not have to share the file and screen shots of the Options menu to manually sync to maintain team consistency on code checkin.

   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

   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

8. Update process

   Hi, this is not related to SQL Prompt only, but to the update process in general.
   As our company firewall is blocking the link in Help "Check for updates ...", I have to submit the "Download a 28 days trial" form and download the full "SQLToolbelt.exe".
   Which is also blocked by the company proxy rules. :-(
   So I have to download the file on my private PC and then copy it to my business machine.
   I assume, my company is not the only one with such precautionary measures.
   Maybe you can implement additional options to download updates.

   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

9. Add quotes and commas function with commas before

   Please can the "Add quotes and commas" action conform to the current active style's Commas setting?

   So if the setting is "Place commas before items", then the action should also place the commas before.

   At the moment, I have to run a Format SQL action after using Add quotes and commas, which is cumbersome.

   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  ·  Format SQL  ·  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

10. Full support for Azure SQL Managed Instance in SQL Prompt

    SQL Prompt should fully support Azure SQL Managed Instances. This includes offering suggestions for all objects (such as system functions, tables, views, etc) which are usable in Managed Instances. For example, CURRENTTIMEZONE and CURRENTTIMEZONE_ID (which were recently implemented in SQL Prompt, but only for Azure SQL Database). All other functions I've tried seem to be working fine, but it would be nice to know that Azure SQL Managed Instance is officially supported by SQL Prompt.

    8 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  ·  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

11. simple tabs (brent ozar)

    https://www.brentozar.com/archive/2011/06/fixing-sql-server-management-studios-tab-text/

    Brent Ozar wrote this tip back in 2011 and I cant believe i've been struggling with the horrible SSMS tabs every day for my whole career. would be great if SQL prompt has a button to change these settings for you or defaults these options when you install it.

    the main reason being that they are buried away and if I wasnt aware of them then i'm sure many others aren't.

    at the end of every day i have about 10 tabs open and i just close the whole lot because it's too hard and to go through them all quickly and i usually have the kids shouting at me for their dinner :)

    https://www.brentozar.com/archive/2011/06/fixing-sql-server-management-studios-tab-text/

    Brent Ozar wrote this tip back in 2011 and I cant believe i've been struggling with the horrible SSMS tabs every day for my whole career. would be great if SQL prompt has a button to change these settings for you or defaults these options when you install it.

    the main reason being that they are buried away and if I wasnt aware of them then i'm sure many others aren't.

    at the end of every day i have about 10 tabs open and i just close the whole lot because it's too hard and to go through them… more

    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  ·  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

12. 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

13. 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

14. 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

15. 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

16. 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

17. Custom Aliases - Ability to Alphabetize by table name

    Custom Aliases - Ability to Alphabetize by table name

    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  ·  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

18. 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

19. 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

20. 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