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

643 results found

  1. When SMSS closes (either by user interaction or unintended closure), SQL Prompt does not save the tabs when I am working in a view. It only saves the tabs that are queries, saved or unsaved. The problem with this is that many times I am creating a view, or working with views. These are never saved with SQL Prompt, so the tab history feature is more or less useless. Redgate needs to include views and unsaved tabs in the recoverable tabs list.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be nice if the new Bulk Formatting or Bulk Code Analysis functionality could also target items directly in the database. This would save time because I wouldn't first have to save objects definitions to my computer.

    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)
  3. Allowing styles or snippets to be shared publicly would be a great feature. This could be potentially be done using GitHub repos and/or Gists.

    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  ·  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 way I work when creating complicated scripts is creating all the SELECT statements and then convert them to CTEs of my final query.
    It would be nice if you could convert SELECT into CTE

    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)
  5. Would it be possible to load built-in functions into the suggestions menu first (or alternatively, ignore keystrokes until the suggestion list is fully loaded)?

    An example scenario is I type "max(" and it picks up the first user-defined object name from the menu. It appears the built-in functions are loaded after the user-defined objects (although they appear at the top).

    In the attached file, the example is that MaxActionId will be selected when I type "max(" too quickly. This is a small but irritating problem because I have to remember to wait momentarily after typing a function name to avoid…

    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  ·  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)
  6. As SQL Prompt user, I want to be able to perform a qualify object names operation on a directory of views, tables, sprocs, etc.

    Currently, one must open a sql file in SSMS first then run the qualify object names operation on each file. This is extremely time consuming. We are trying to improve our code quality and readabily by following best practices.

    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)
  7. Add a menu Item option to unformat a query. In other words take the query that is highlighted or every query in the script and convert them to be on a single line with only a single space between keywords, words, and operators.
    This would be very useful for having to copy SQL into a table or other some object that shouldn't have normal formatting in it.
    An option would be to double up all single quotes, so that the query can be placed between single quotes.

    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

    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)
  8. SQL Prompt does not start a new line for the SELECT portion of a CTAS statement within Azure Synapse Analytics when there is a defined distribution or index using a WITH clause. Instead the SELECT statement is tabbed way over to the right.

    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

    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)
  9. I would like to be able to specify different script blocks inside a snippet that would work differently based upon the sql server version of the server I am connected to.

    Or.... optionally have a version indicator on the snippet to perform the same thing. Then if two snippets share the same name it would apply the correct one based upon version.

    EX:

    :if $version_major$ >= 13
        CREATE OR ALTER PROCEDURE [$dbo$].[$proc_name$] (@param1 INT) AS BEGIN
            $CURSOR$SELECT @param1
        END
        GO
    :else 
        IF OBJECT_ID('[$dbo$].[$proc_name$]', 'P') IS NULL BEGIN
            EXEC('CREATE PROCEDURE [$dbo$].[$proc_name$] AS BEGIN SELECT 1; END;')
        END 
    
        GO
        ALTER PROCEDURE [$dbo$].[$proc_name$]
    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  ·  User interface  ·  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. It would be very useful to be able produce where clause from copied horizontal selection from the results grid. For example from the uploaded image, where clause should be

    WHERE CTA.TRANSACTIONDATE = '2021-06-27'
    AND CTA.TRANSACTION
    TYPECODE = 52
    AND CTA.ITEM
    CODE = 1500012200
    AND CTA.ITEMBARCODE = '8001841964966'
    AND CTA.YOUR
    COMPANYCR = 104183
    AND CTA.OTHER
    ENTITY_CR = 46084

    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)
  11. Since there is no listing for SQL Doc requests, I was advised by support to enter this under SQL Prompt. When generating the documentation for stored procedures, functions or views, the "Uses" section only includes objects from the same database where the procedure resides. We have many objects that use tables located in other databases so it would be extremely helpful if SQL Doc could include them in the "Uses" section of the documentation.

    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  ·  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. Qualify object names [Ctrl+B;Ctrl+Q] should also clean up three and four part column references

    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)
  13. Be able to refactor INSERT statement into UPDATE statement that has SELECT rather than VALUES i.e. "insert into xxx select from".

    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

    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)
  14. It would be appreciated if you could enhance the SqlPrompt Formatting Styles functionality. I believe this would go in the STATEMENTS >>> Data (DML) section.

    I'd like to continue using the "If there are multiple expressions" item of the "Place GROUP BY / ORDER BY expression on new line" drop-down. But I'd like those expressions to be indented; they presently all left-align to the GROUP BY.

    Also, while you're there, it seems that it would be good to also have add an "If longer than wrap column" option to the above-mentioned drop-down.

    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

    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)
  15. The current parenthesis options I have set for an INSERT INTO (DML) statement, only appear to work for the list of columns, but NOT for the list of values in the VALUE clause. I'm unsure why this behaviour is different, but this inconsistency seems like a bug.

    I have provided a screenshot where you can clearly see the parentheses are not aligned correct in comparison with the INSERT statement.

    Ultimately I would like for the formatting to be overall consistent.

    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

    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)
  16. For tabs with an open connection, show the SPID # in the list on the left side

    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

    0 comments  ·  Tab history  ·  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. 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

    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  ·  Tab history  ·  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. Consider a table
    CREATE TABLE [dbo].[ItemGroups](
    [Group] [VARCHAR](25) NOT NULL,
    [Description] [VARCHAR](25) NOT NULL)

    SELECT Group from dbo.ItemGroups ->

    Incorrect syntax near the keyword 'Group'.

    Would be nice to get a warning when a column name is a reserved word. Square brackets make the syntax valid but unnecessary if a column is named more accurately, e.g. ItemGroupCode

    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. I was a bit surprised that SQL Prompt does not Identify and highlight duplicated variable names. Seems like an important omission.

    Please extend the 'Find Unused Variables' to include identifying any duplicated variable names.

    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. Allow dark theme for all GUI interfaces in Prompt.

    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)
1 2 6 8 10 32 33
  • Don't see your idea?