Skip to content

SQL Prompt

Welcome to the SQL Prompt feature suggestion list. Find out more information about SQL Prompt at http://www.red-gate.com/products/sql-development/sql-prompt/.

If you have any questions, need help or have found a bug in SQL Prompt, please visit the forums or our support portal.

SQL Prompt

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

274 results found

  1. It would be nice to have sortable columns in the table popup. This way we can see them in ordinal order (as it exists now), or order them alphabetically (or even by data type). Hopefully not much harder than changing a grid column property.
    This would make it much easier for our Oracle folks to accept using SSMS, as it seems all Oracle tools do this by default. It would also shut them up. :) :)

    1 vote

    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)
  2. Due to the length of some of the queries I write, I have to edit the file RedGateSqlPromptEngine_EngineOptions.xml manually. It would be nice to be able to edit the values for ParserLookBackDistance and ParserLookAheadDistance in the Options menu. I understand the drawbacks of making these values too large. If they were in the Options menu I could adjust them for a long query and then set them back for shorter queries.

    3 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The suggestions list after the TRIGGER is full of triggers. SQL Prompt, having been given the schema and table should narrow that list to only those present on the table to be ALTERed.

    I would categorize this as a bug, rather than a suggestion...

    5 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. The options to "Only load suggestions for certain databases" and "Don;t load suggestions for certain databases" are nice, but it'd be really useful to also be able to include or exclude on a per schema basis.

    34 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)
  5. If I edit a statement like SELECT COALESCE(x, y, z) and then add some parenthetical as in LTRIM(COALESCE(x, y, z)), the last parenthetical is deleted by SQL Prompt even though I typed it. Two options are to 1) correctly establish parenthesis or 2) stop deleting characters I type correctly

    12 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would be nice to have a placeholder that, when the snippet was used, was replaced with a new GUID. For example:

    INSERT audit.Changes (Id, Date, Reason)
    VALUES ('$GUID$', '$DATE$', '$CURSOR$')

    2 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)
  7. When a --#TODO: or --#HACK is written on our code, it could be helpful to highlight it in order to give an alert to the reader. In addition it can be very helpful to let the user to configure the pattern (i.e. --#MyTerm).

    46 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

    3 comments  ·  Format SQL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Thomas Walsh responded

    We’ve released support for highlighting TODOs in version 9 of SQL Prompt as part of its new code analysis feature.

    You can get the latest version of SQL Prompt from https://www.red-gate.com/products/sql-development/sql-prompt/.

    We’re marking this request as completed, but if you feel strongly about being able to configure the term, please feel free to open a new suggestion.

    Kind regards,

    The Prompt Team

  8. It would be nice to have the code within a BEGIN TRAN and COMMIT be indented.

    BEGIN TRAN
    <ssss>INSERT....
    <ssss>UPDATE....
    COMMIT TRAN

    6 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

    4 comments  ·  Format SQL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Similar to the existing Qualify Object Names and the other pending request to fix case of all object names, I would like to have an option to add brackets added to all database object names (columns, tables, schemas) where they are missing.

    13 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

    4 comments  ·  Format SQL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Intellisense should find snippets where characters appear anywhere in the snippet name, not just at the beginning. I have 2 or 3 dozen snippets and I can't always remember what the less frequently used snippets are called. For example I might several snippets that deal with space usage, but some are named like this: "getSpaceUsage". It would be useful if typing "space" found all snippets that contained space anywhere in the name not just at the beginning.

    4 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)
  11. When formatting a case statement I want the case keyword to show in uppercase just like the when and end keywords. Now initially it uppercases CASE but when running SQL format it turns it to lowercase (bug?) See example below of the current format behaviour.

    SELECT case WHEN 1 = 1 THEN 1
    ELSE 0
    END

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. please add support for sql 2014 ctp2, i'm already using it and im sure others are as well and quite frankly i've grown very accustomed to using sql prompt that it became quite hard to work without it.

    i hope you can add the support really soon

    9 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

    completed  ·  5 comments  ·  Intellisense  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. The SQL formatter was one of the reasons we chose to buy the Developer Toolkit, but it doesn't seem to be able to be configured to format to our company style.

    An example of the style is here: http://pastebin.com/LTLRJ6Fb

    Notably, it would be good to be able to have the FROM and table name on the same line without excess white-space in between,

    7 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)
    completed  ·  Andrei Rusitoru responded

    This feature was released in version 8 of SQL Prompt.

    If there are any missing features please let us know by creating a new suggestion.

    Kind Regards,
    The Prompt Team

  14. Currently any comments that appear before the ALTER PROC statement are not scripted by SQL Prompt which results in those comments being silently deleted if the alter statement is executed.

    If I hover the mouse over a stored procedure name and click on the procedure name that pops up in order to see the script window I can see these comments but if I type alter proc <procname> and press tab to produce an alter script these comments are missing.

    There is a danger here of losing comments without the user being aware of it. I think SQL Prompt should…

    8 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)
  15. Currently when formatting a Create table command the SQL Prompt is moving the "Default" to a next line and indenting it...
    like this
    [insertDT] DATETIME NULL
    [______INDENT] DEFAULT GETDATE()
    ,[ActualMU] INT NULL
    [
    ___INDENT]DEFAULT 0
    ,[PlannedMu] INT NULL
    [
    ___INDENT]DEFAULT 0
    ,[CompletedDT] DATETIME NULL
    [
    ___INDENT___] DEFAULT GETDATE()

    And the format that I would like to see (making easier to read) is
    keeping all definition of each field in the same line, like

    ,[insertDT] DATETIME NULL DEFAULT GETDATE()
    ,[ActualMU] INT NULL DEFAULT 0
    ,[PlannedMu] INT NULL DEFAULT 0
    ,[CompletedDT] DATETIME NULL DEFAULT…

    5 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Andrei Rusitoru responded

    This feature was released in version 8 of SQL Prompt.

    If there are any missing features please let us know by creating a new suggestion.

    Kind Regards,
    The Prompt Team

  16. After upgrading to SQL Prompt 6 (6.1), I notice reduced performance and I occasionally get "SQL Prompt cannot retrieve objects from <some database name>. (etc)", which reference a database that I do not use or am ever likely to use and IIRC have never used. It seems SQL Prompt is trying to cache objects for all databases on the connected server. That would be overkill, and only serves to slow it down and cause errors such as the one mentioned.

    3 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Aaron Law responded

    This was likely due to the synonym support added in 6 which will try to offer suggestions by loading databases that the synonyms are referencing. In the latest build of Prompt this is optional (under Suggestions→Connections) and off by default.

  17. Typically, the GROUP BY column list is exactly the same as the SELECT list except the aggregates and any constants included. I usually wind up using a copy & paste, which is always a hassle, especially if it is a complex query. It always seemed to me that the GROUP BY list should be optional in the SQL standard. But short of a standard change followed by implementation changes, it would be nice to at least have it defaulted for me.

    By the same token, the HAVING statement could (optionally) prepopulate with (one of) the aggregate(s) from the select list.…

    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)
  18. The SQL Prompt formatter incorrectly tries to capitalize (whether automatically while I type or using the formatter) system functions that are missing a database prefix. For example, SQL Prompt doesn't try to capitalize:

    sys.fn_listextendedproperty

    but it WILL capitalize

    fn_listextendedproperty

    as soon as I hit space, regardless of the CASE setting in SQL Prompt's options. Obvious, a capitalized FN_LISTEXTENDEDPROPERTY does not work: the function is case-sensitive.

    There does not appear to be a way around this, not even by setting Format -> Styles -> Case -> Buit-in functions to "Leave as is". That only resolves the problem for the manual formatter:…

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Aaron Law responded

    This is fixed in the latest build of Prompt, if you’re still having problems please let me know.

  19. I used to have a couple hundred milliseconds of delay in here. This was really helpful in some circumstances to allow me to do down a line of text adding tabs, spaces, commas, etc. (all kinds of things to satisfy my obsessive need for proper formatting). Without this option I now have to hit [ESC] each time to clear the suggestion box no matter how quick I move down, making this an annoyance.

    6 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)
  20. When a word is entered in a comment block, that is the same as a keyword (e.g. FROM), SQL Prompt should not automatically convert the word to uppercase.

    5 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?