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

276 results found

  1. SQL Prompt does not recognize the new ROWS | RANGE keyword additions to the OVER clause in SQL Server 2012

    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)
  2. When object names appear in the candidate window for an autocomplete, the schemas are not shown by default. Clicking on the the arrow in the bottom left of the window will show them, but this setting is not remembered so you have to do it each time. Also there's no keyboard shortcut that I can find to do this. Add the ability to set this popup to show the schema names by default.

    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)
  3. For any attempt to use Intellisense within a RAISERROR() there is no prompting - list says "No suggestions".

    Sample:
    RAISERROR('Not at 12hrs UTC - time is %s',0,1,@<<Nothing-here>>) WITH NOWAIT

    Also reported as a defect on the SQL Prompt Forum

    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)
    completed  ·  Aaron Law responded

    The latest version of Prompt should give you suggestions within a RAISEERROR

  4. Need Intellisense for the spatial functions and geography/geometry data types, especially since they are case sensitive, and annoyingly a mixture of upper and lowercase.

    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

    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)
  5. When copying a list of items from something like Excel, it would be lovely to have a feature in Prompt which would highlight the list, hit a key stroke and it would place quotes around each item and a comma after them.

    It would stop me bashing the quote + arrow + comma keys at the speed of light.

    22 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

    9 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)
  6. Don't expand wildcard occurrences within EXISTS clause.
    WHERE EXISTS(SELECT * FROM tab1)
    should not expand to
    WHERE EXISTS(SELECT col1, col2, col3 FROM tab1)

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I would like the ability to get Format SQL to handle my JOIN formatting - I like to have my JOINs look like this:

    SELECT
    (columns)
    FROM
    sys.tables t
    INNER JOIN
    sys.indexes i ON t.OBJECTID = i.objectid

    That is: I want to have my tables being joined lined up with the (intended) table in the FROM clause, and I like to have my JOIN condition on the same line as the joined table.

    Right now, I cannot seem to get this to work - the table name and join condition are always stuck onto the same line as…

    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

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

  8. When the WITH clause is specified in the FROM clause on a JOIN, Format SQL pushes the join condition out to the WITH.
    Like this:
    FROM
    TableA WITH (NOLOCK)
    JOIN TableB WITH (NOLOCK)
    ON TableA.ID = TableB.ID

    I would like it to behave like it does when the WITH is not present

    FROM
    TableA WITH (NOLOCK)
    JOIN TableB WITH (NOLOCK)
    ON TableA.ID = TableB.ID

    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

    2 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. When disabling SQL prompt (or when a trial ends) the default SSMS intellisense is not getting back to work.
    This is especially important since there are a lot areas that the native SSMS intellisense is much better than SQL prompt (I will try to post all of them), so one might try to take advantage of it.

    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)
  10. I'm finding my comments are hanging out all on their own after the rest of my code is formatted. I would request a feature to allow comments to indent to the same level as the code on the line below.

    56 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

    5 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)
  11. Or maybe an option to disable parsing of statements using CTEs. My keyboard takes seconds to respond when several CTEs are in the script.

    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)
    completed  ·  Aaron Law responded

    We’ve just released SQL Prompt 6.1 which shouldn’t slow down typing when CTEs are used

  12. Please add formatting options for the deferent parts of the MERGE command like you have for INSERT

    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

    1 comment  ·  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)
  13. Please see forum thread http://www.red-gate.com/MessageBoard/viewtopic.php?t=14749

    I ran into what I would consider a serious issue with the Script Object as ALTER feature. A few hours earlier I had changed a stored procedure script and executed the Alter script so the change was now "active".

    A few hours later, within the same SSMS application (but different query window) I used the right-click Script Object option as a shortcut so I didn't have to scroll through a very long list in Object Explorer... Unfortunately it scripted the OLD version of the procedure and not the one changed hours earlier.

    Now, I know…

    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)
    completed  ·  Paul Stephenson responded

    As of SQL Prompt 5.2.8, Script as ALTER will always fetch the script directly from the database.

  14. We use a separate schema (z_audit) to capture data changes from dbo tables as a complete audit trail. The tables in each schema are named the same. Every time I come to the suggestions list, I either take it as read that the top table listed is in the dbo schema, or must click that little arrow at bottom-left to "show schema", involving having to grab the mouse just to expose the schema when we're supposed to be efficiently keying; no mousing involved unless we need to use a different suggestions tab...

    An option that toggles this to OUR preference…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. In SSMS when accessing a table that is not in the current database (using the three part convention) then no intellisense is coming up for the fields (such as in the where clause)

    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)
    completed  ·  Thomas Walsh responded

    SQL Prompt now supports suggestions from other databases when using the three part convention.

    Kind Regards,

    The Prompt Team

  16. I believe the DISTINCT keyword should remain on SELECT line but at least maintain the indentation please. Thanks

    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

    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)
  17. It would be nice to select a small already formatted script, and unformat it by putting it into one line.

    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  ·  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)
  18. I'd like to enable schema collection when I'm writing code, and disable it when I'm doing adhoc queries. Why: We have 100 identical databases with 1900 tables in each database. When I run a query that pulls data from each database sqlprompt starts collecting schema data from all 100 databases, then it runs out of memory and crashes.

    The "Turn Off Prompting" option does not help.

    example:

    select id,customer from DB1.dbo.orders where date > @d
    union select id,customer from DB2.dbo.orders where date > @d
    ...etc...

    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)
  19. If you go
    SELECT * FROM sys.tables AS t
    or
    SELECT * FROM sys.tables AS [t]

    then intellisense will happily carry on working correcly, with t. now showing object members.

    However

    SELECT * FROM sys.tables AS "t"
    and
    SELECT * FROM sys.tables AS 't'

    both cause the intellisense to give up for the rest of the batch. All four identifier markups are valid (for now) and should be treated equally...

    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)
  20. Please add support for SQL CMD mode. When SSMS is in SQL CMD mode, SQL Prompt pretty much becomes disabled when :setvar is used to define an object (e.g. table) name. Thus, in the code:

    :setvar mytable "dbo.mytable"
    select * from $(mytable)

    SQL Prompt is of no use. SQL Prompt should be able to resolve $(mytable) to the base object.

    17 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)
  • Don't see your idea?