277 results found

1. suggestion box is sometimes in the way

   The intellisense box often obscures data in the grid results payne which requires that I hit esc to close suggestions and then retype or ctrl-space to bring it back up.

   Possible solutions:

   1) The main reason is that the box is usually much larger than it needs to be. If it would auto size as needed it would take up much less room.

   2) an optional transparency setting would be much appreciated. Initially draw the box opaque but when the user stops typing, start fading it out a bit slowly because the user may want to see content below. The initial opacity would be configurable.

   The intellisense box often obscures data in the grid results payne which requires that I hit esc to close suggestions and then retype or ctrl-space to bring it back up.

   Possible solutions:

   1) The main reason is that the box is usually much larger than it needs to be. If it would auto size as needed it would take up much less room.

   2) an optional transparency setting would be much appreciated. Initially draw the box opaque but when the user stops typing, start fading it out a bit slowly because the user may want to see content below. The… more

   21 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  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

   Transparency was added as an option in SQL Prompt 9.4.10.

2. Extend the column toolstips with the nullable attribute

   Extend the column toolstips with the nullable attribute, like this "ic.Attachment varchar(max) not null (Column)"

   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

   1 comment  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  Aaron Law responded

   This is included in SQL Prompt 6.4, which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

3. Intellisense for system stored procedures

   I just needed to re attach a database from a single mdf file. Something I do every 6 months or so and every time I have to google the command and its syntax. Would be helpful so SQL Prompt recognised and helped with these and other inbuilt procedures and their parameters, for example:

   spattachsinglefiledb

   sp_helptext

   spattachdb

   23 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  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  Aaron Law responded

   In 6.4 we always provide intellisense for system stored procedures if the query is being run against master.

   If you’re running against a normal db then we hide the system stored procedures by default as they clutter the suggestions list. There’s a couple ways to get around this, either by qualifying with “sys.” or using the “List system objects” option. A video on this can be found here https://www.youtube.com/watch?v=i8DOTmHkKo8

4. sql prompt write my code if I show it the requirements
   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  ·  Delete…  ·  Admin →
   completed  ·  Thomas Walsh responded

   We’ve released support for static code analysis mentioned in the comments in version 9 of SQL Prompt.

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

   If there is something missing please let us know by opening a new suggestion.

   Kind regards,

   The Prompt Team

5. inserted and deleted tables should be supported in triggers

   There is currently no support for the 'inserted' and 'deleted' tables within triggers. They should be treated as equivalent to the original table that the trigger is attached to.

   37 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  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  Aaron Law responded

   This is included in SQL Prompt 6.3, which can be downloaded from http://www.red-gate.com/products/sql-development/sql-prompt/

6. Lower-Case Keyword Support in Format SQL

   Support lower-casing keywords instead of upper-casing them; this makes reading the query far easier as the app-specific bits are more visible

   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

   2 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   completed  ·  Aaron Law responded

   This already exists as an option in SQL Prompt

7. CTE Support

   It would be nice if SQL Prompt could parse CTE expressions and provide prompts just like for regular tables

   14 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  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  Justin Caldicott responded

   This issue has been reported non-reproducable in recent versions of SQL Prompt.

8. add semi colon to insertion keys

   Could we have a check box to allow us to have the semi colon as one of the insertion keys (Main->Behaviour)?

   It's not as common as the other keys there but when I'm about to finish a script I can't just hit the semi colon key.

   12 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

   4 comments  ·  Intellisense  ·  Delete…  ·  Admin →
   completed  ·  Aaron Law responded

   We’ve added semi colon to the list of insertion keys in 6.2 which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

9. Qualify column names with table aliases only

   I would like an additional option for the Inserted code > Qualification tab:

   Qualify column names with table aliases only.

   Most times I want to assign a table alias and use it when adding columns, however if I forget to assign a table alias or remove it, I don't want a fully qualified table name when using the Qualify column names with table name option.

   I would like the option to qualify with both table names and table aliases or just table aliases and NOT table names.

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

   This is included in SQL Prompt 6.4, which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

10. Add ability to include earlier tables in the Join Clause

    When writing a query that joins to several tables, the Join Clause only seems to look at the previos table to determine what columns can be used to join on. For example, when typing out the following query:
    SELECT * FROM [dbo].[employee] AS E
    INNER JOIN [dbo].[Department] AS D
    ON [E].[DepartmentID] = [D].[DepartmentID]
    INNER JOIN [dbo].[Position] AS P
    ON ...

    When I look at the options for the ON clause for the join to Position, it doesn't include any columns being joined back to the Employee table. It would be nice if the suggestions would include at least any foreign key relationships so that if I have a FK between Position & Employee it would include that in the suggestions

    When writing a query that joins to several tables, the Join Clause only seems to look at the previos table to determine what columns can be used to join on. For example, when typing out the following query:
    SELECT * FROM [dbo].[employee] AS E
    INNER JOIN [dbo].[Department] AS D
    ON [E].[DepartmentID] = [D].[DepartmentID]
    INNER JOIN [dbo].[Position] AS P
    ON ...

    When I look at the options for the ON clause for the join to Position, it doesn't include any columns being joined back to the Employee table. It would be nice if the suggestions would include at least any foreign… more

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

    We’ve released SQL Prompt 6 which includes all tables in a join clause.

11. Ability to flip the sides in an auto generated join clause

    When I write a join statement I put the last table that I am joining to the other tables on the left side of a join clause. For example:
    SELECT *
    FROM tblOrder o
    INNER JOIN tblIOrder_Detail d
    ON d.OrderID = o.OrderID
    The auto-generated join clause would be "ON o.OrderID = d.OrderID". It would be nice if it was possible to customize this behaviour to choose which side there will be each table/alias on.

    Thanks

    27 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

    5 comments  ·  Intellisense  ·  Delete…  ·  Admin →
    completed  ·  Aaron Law responded

    We’ve released SQL Prompt 6 which includes an option to swap the order of columns in join clauses.

12. XML Data Type method layout SQL support

    Can not use SQL prompt to layout XML data type functions, for example this statement:

    SELECT(SELECT 1 Col
    FOR XML PATH(''), TYPE).value('.', 'VARCHAR(MAX)')

    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

    completed  ·  1 comment  ·  Format SQL  ·  Delete…  ·  Admin →

13. select column names

    after typing select and adding table name the popup box that shows the table summary (column names and their types); if these rows(column names) be clickable, select columns could be filled from that list instead of typing.

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

    SQL Prompt contains a “Column Picker” feature that should do what you’re requesting.

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

    If there is something missing please let us know by opening a new suggestion.

    Kind regards,
    The Prompt Team

14. toggle SQL Prompt from toolbar

    I frequently need to work on longer procedure or scripts, and the longer the script gets Sql Prompt gets more and more bogged down, to the point I just turn it off. It would be nice to be able to toggle it from the toolbar rather than open the options to un-check 'Use SQL Prompt'

    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

    completed  ·  0 comments  ·  User interface  ·  Delete…  ·  Admin →

15. Column aliases alignment

    Allow alignment of column aliases in a Select statement.

    22 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

    4 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    completed  ·  Andrei Rusitoru responded

    This feature is now included in the new SQL Prompt 8.0. For additional information see: http://documentation.red-gate.com/display/SP8/SQL+Prompt+8.0+release+notes

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

    Thank you for your help!

16. Provide support for CLR functions

    The object text exists as normal for CLR functions (or at least enough for provide auto suggest on object name and number of params and types), therefore please can function which are backed by CLR be available in the suggestion list

    47 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

    8 comments  ·  Intellisense  ·  Delete…  ·  Admin →
    completed  ·  Aaron Law responded

    This is included in SQL Prompt 6.4, which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

17. Moving commas from "end" to "start" is always buggy when comments exist

    Moving commas from "end" to "start" or vice-versa is buggy when comments exist after each column or parameter. This is an issue regardless of the type of statement (SELECT, INSERT, UPDATE, CREATE TABLE/VIEW/FUNCTION/STORED PROCEDURE, etc).

    Here is my original SP with commas at "end" followed by comments (hyphens are used for indentation due to HTML formating issues):
    CREATE PROCEDURE dbo.MyProcedure
    ---- @Param1 int, --Param1 comments
    ---- @Param2 int, --Param2 comments
    ---- @Param3 int --Param3 comments
    AS
    BEGIN
    ---- SELECT Col1 , --Col1 comments
    ---- ---- Col2 , --Col2 comments
    ---- ---- Col3 --Col3 comments
    ---- FROM MyTable
    ---- RETURN
    END
    GO

    After CTRL+K+Y, the commas and comments are incorrectly placed on their own separate line:
    CREATE PROCEDURE dbo.MyProcedure
    ---- @Param1 int
    ---- , --Param1 comments
    ---- @Param2 int
    ---- , --Param2 comments
    ---- @Param3 int --Param3 comments
    AS
    ---- BEGIN
    ---- ---- SELECT Col1
    ---- ---- ---- , --Col1 comments
    ---- ---- ---- Col2
    ---- ---- ---- , --Col2 comments
    ---- ---- ---- Col3 --Col3 comments
    ---- ---- FROM MyTable
    ---- ---- RETURN
    ---- END
    GO

    Alternatively when moving commas from "start" to "end" the commas are placed on their own line, but at least comments follow the statement. Going from either direction, this formatting is both ugly and unproductive. Moving comments to a new line is confusing! Either way this buggy issue robs us of valuable vertical screen space.

    We regularly receive code that needs to be re-formatted to our own preferences. Please modify SQL Prompt to always leave both commas AND comments on the same line but still move commas to our preferred location ("start" or "end").

    Thank you.

    Moving commas from "end" to "start" or vice-versa is buggy when comments exist after each column or parameter. This is an issue regardless of the type of statement (SELECT, INSERT, UPDATE, CREATE TABLE/VIEW/FUNCTION/STORED PROCEDURE, etc).

    Here is my original SP with commas at "end" followed by comments (hyphens are used for indentation due to HTML formating issues):
    CREATE PROCEDURE dbo.MyProcedure
    ---- @Param1 int, --Param1 comments
    ---- @Param2 int, --Param2 comments
    ---- @Param3 int --Param3 comments
    AS
    BEGIN
    ---- SELECT Col1 , --Col1 comments
    ---- ---- Col2 , --Col2 comments
    ---- ---- Col3 --Col3 comments
    ---- FROM MyTable
    ---- RETURN
    END… more

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

    This feature is now included in the new SQL Prompt 8.0. For additional information see: http://documentation.red-gate.com/display/SP8/SQL+Prompt+8.0+release+notes

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

    Thank you for your help!

18. Auto generated INSERT statement is buggy with commas at start

    The auto-generated INSERT statement BADLY MISALIGNS data when "Place commas at start" is enabled. I've listed all the settings to reproduce the issue at the end of this post.

    The comma and associated info are on a separate line (almost useless - Worse when I need to delete some of the columns). See this example (generated by SQL Prompt Pro 5.1 - hyphens represent tabs due to HTML limitations):

    INSERT INTO dbo.Test
    ---- (FirstName
    ---- , LastName
    ---- , LocationAddress
    ---- , LocationCity
    ---- , LocationState
    ---- , LocationZip)
    VALUES (''
    ---- , -- FirstName - varchar(100)
    ---- ''
    ---- , -- LastName - varchar(100)
    ---- ''
    ---- , -- LocationAddress - varchar(100)
    ---- ''
    ---- , -- LocationCity - varchar(100)
    ---- ''
    ---- , -- LocationState - varchar(50)
    ---- '' -- LocationZip - varchar(10)
    ---- )

    When "Place commas at end" is enabled it works correctly. Please fix the "place commas at start" option to work like this, but with preceeding commas of course:

    INSERT INTO dbo.Test
    ---- (FirstName,
    ---- LastName,
    ---- LocationAddress,
    ---- LocationCity,
    ---- LocationState,
    ---- LocationZip)
    VALUES ('', -- FirstName - varchar(100)
    ---- '', -- LastName - varchar(100)
    ---- '', -- LocationAddress - varchar(100)
    ---- '', -- LocationCity - varchar(100)
    ---- '', -- LocationState - varchar(50)
    ---- '' -- LocationZip - varchar(10)
    ---- )

    You can reproduce this issue with the following settings from the SQL Prompt menus:

    Format > Commas and Parentheses:
    ----"Place commas at start"

    Inserted Code > Objects & Statements:
    ----"Insert full INSERT statement"
    --------"Show column names" and/or "Show column data types"
    --------"Insert default value for each column"

    The auto-generated INSERT statement BADLY MISALIGNS data when "Place commas at start" is enabled. I've listed all the settings to reproduce the issue at the end of this post.

    The comma and associated info are on a separate line (almost useless - Worse when I need to delete some of the columns). See this example (generated by SQL Prompt Pro 5.1 - hyphens represent tabs due to HTML limitations):

    INSERT INTO dbo.Test
    ---- (FirstName
    ---- , LastName
    ---- , LocationAddress
    ---- , LocationCity
    ---- , LocationState
    ---- , LocationZip)
    VALUES (''
    ---- , -- FirstName - varchar(100)
    ---- ''
    ----… more

    11 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

    5 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    completed  ·  Aaron Law responded

    This is included in SQL Prompt 6.4, which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

19. Format SQL to Match Object Case

    If I had the table [Address] that had the columns StreetAddress1, StreetAddress2, City, State and ZipCode defined and the following existing code was formatted:

    SELECT streetaddress1,
    streetaddress2,
    CITY,
    zipcode
    FROM [address]

    I would like to see SQL Prompt match the case of the underlying object such that the results after formatting would be:

    SELECT StreetAddress1,
    StreetAddress2,
    City,
    ZipCode
    FROM [Address]

    This should apply to all underlying objects (procedures [name and parameters], tables [columns, index names (used in hints), etc., functions and views; and anything else I forgot). It should also apply to variables defined within a procedure (e.g. DECLARE @MyValue INT... SET @myvalue = 3. Subsequent SET/SELECT or other use of the variable should be formatted to match the case in the DECLARE statement so that the SET above would be formatted to SET @MyValue = 3).

    If I had the table [Address] that had the columns StreetAddress1, StreetAddress2, City, State and ZipCode defined and the following existing code was formatted:

    SELECT streetaddress1,
    streetaddress2,
    CITY,
    zipcode
    FROM [address]

    I would like to see SQL Prompt match the case of the underlying object such that the results after formatting would be:

    SELECT StreetAddress1,
    StreetAddress2,
    City,
    ZipCode
    FROM [Address]

    This should apply to all underlying objects (procedures [name and parameters], tables [columns, index names (used in hints), etc., functions and views; and anything else I forgot). It should also apply to variables defined within a procedure (e.g. DECLARE @MyValue… more

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

    This is included in SQL Prompt 6.4, which you can download from http://www.red-gate.com/products/sql-development/sql-prompt/

20. Create more $...$ placeholders for snippets

    I would like to see additional placeholders for the snippet manager. For example $DBNAME$, $SERVER$, $PASTE$ (already suggested). A format option for $DATE$ and $TIME$ would also be nice (e.g. $DATE(mm/dd/yyyy)$ $TIME(hh:mm:ss24/hh:mm:ssA/hh:mm)$, etc.).

    39 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

    6 comments  ·  Delete…  ·  Admin →
    completed  ·  Aaron Law responded

    We’ve released SQL Prompt 6 which includes several new placeholders.