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.

How can we improve SQL Prompt?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. "drop user"

    Highlight of today was when I ran

    DROP USER MyUser

    In the wrong (production) database.

    Please add a warning to SQL Prompt, like your
    "You're about to execute a DELETE statement without a WHERE clause"

    When you run a DROP USER or a DROP LOGIN statement on a production server. Not only does the user or login disappear, but also all rights granted to the user.

    Maybe add the question “are you in the correct database?”

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  2. Autofix for existing functionality

    There are cases where the code analysis detects errors and where the tool already have functionality to correct the issue. For instance with unqualified column names

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  3. Autofix with shortcut

    A shortcut to implement the autofix changes.
    Would be nice if it wasn't necessary to use the mouse when applying autofixes.

    It is almost there; you can press ctrl and get the error window and even just press enter then, to apply the fix. But the window stays and there is no reason to actually open the window, the fix could/should just be applied

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  4. Mark same columns in JOIN conditions

    It helps avoiding join on the same column (especially at inner join).
    Example:
    UPDATE A SET Column1 = B.Column2 FROM TableA AS A INNER JOIN Table B ON A.Column3 = A.Column3.
    It happens usually by accident. The statement should be:
    UPDATE A SET Column1 = B.Column2 FROM TableA AS A INNER JOIN Table B ON A.Column3 = B.Column3.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  5. DEP026, updated to work with spatial code

    w.sysLocationXY.STX, should not generate an code analysis error.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  6. Implement all SQL Code Guard Rules in SQL Prompt Code Analysis

    There are several rules that are only available in SQL Code Guard. And with SQL Code Guard no longer being maintained they should be implemented in SQL Prompt Code Analysis so that we can avoid having to use two products.

    By our count here are the rules currently not implemented in Code Analysis:

    DEP004 COMPUTE and COMPUTE BY clauses are deprecated
    DEP005 FASTFIRSTROW table hint is deprecated
    DEP008 PASSWORD/MEDIAPASSWORD options in BACKUP/RESTORE statement are deprecated
    DEP010 DBCC CONCURRENCYVIOLATION is deprecated
    DEP017 NON-ANSI join (*= or =*) is used
    EI001 Incompatible variable type for procedure call
    EI002 Incompatible literal type for…

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to run Code Analysis against whole DB

    With the deprecation of SQL Code Guard and it's replacement by Code Analysis there is one feature that we heavily used that is now no longer there, and that is the ability to run SQL Code Guard against the whole DB not just the query on the screen.

    This allowed us to investigate new DBs that we'd inherited to see what sort of cleanup we might be looking at as well as giving us the ability to see if anything had snuck in to our existing DBs without going file by file.

    I know there are other tools (like SQL…

    12 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  8. PE019

    I'd like to vote for adding PE019 (Consider using EXISTS instead of IN) to the issues which can be auto-fixed.

    It feels like the kind of re-write that would probably be simpler for a computer to do than a person.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  9. SQL Prompt Code Visualization (Like Flow Chart)

    SQL Prompt should be able to Visualize the Code and represent the code like Flow Chart.
    This Feature will be very useful while working with heavy Stored Procedures.
    The Sample Code Visualization image is shared below:
    --
    https://drive.google.com/file/d/1dE0H7UP1MOuOZ4A3e4urUkDlR0FD4474/view?usp=sharing
    --

    13 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  10. Issue code SC003 when USE is first line

    Issue code SC003 shouldn't happen if the USE statement is at the top of a SQL script.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make SQL Prompt & SCG Command line ignore code where scgignore is set

    We have adopted SCG and have commented out areas of code we do not want checking with scgignore. The new version of SCG command prompt and SQL Prompt do not recognise these comments, and report the area of code with warnings.
    Please amend so they are not reported, or at least reported differently so we can ignore.

    0 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  12. sonarqube

    Have SonarQube plugin that will do code analysis using your rules rather than TSQL or PLSQL plugins

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow custom rules for code analysis

    SQL Prompt has the ability to catch and warn about Update statements without Where clauses.

    How about something similar that catches and warns about security commands like Grant or Deny.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  14. DECIMAL default scale warning in Code Analysis

    Would be great if SQL Prompt Code Analysis would give a warning on SQL Below:

    SELECT CAST( 1.453 AS DECIMAL)
    SELECT CONVERT(DECIMAL, 1.453 )

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  15. EXEC sp without return (EXEC @Results = sp)

    EXEC sp_who2 without return (EXEC @Results = sp_who2)
    Give a warning when tsql or stored procedure has execute a stored procedure without a variable for an error to bubble up to.

    This is the proper way because ieven in a try catch the Exec sp_who2 won't give and error to stop the tsql from going on

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add rule for deprecated DATABASEPROPERTY

    Add rule for deprecated DATABASEPROPERTY

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  17. Offline TSQL code analysis and Standardization report..Where we can add custom rules regarding to company naming procedure

    My Name is Waleed Abrar and my license number is. I am actively looking of Static TSQL Analysis and I was really happy with the SQL Prompt. I have done some analysis and implemented some test cases. It works really good working live and parallel to development . I want to ask if it’s possible to do an offline analysis and get a HTML or Excel report for a particular database about the TSQL code Quality inside the DB. For Example I can select the Database ‘XYZ’ and then click Analyze static code. It will give me a report back…

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  18. Inconsistently Advised to Use Alias For CTE (ST010)

    Simple statements do not flag this:

    WITH CTE1 AS (SELECT TestColumn FROM dbo.TestTable)
    SELECT a.TestColumn FROM CTE1 a
    INNER JOIN CTE1 b ON a.TestColumn = b.TestColumn;

    However, more complex statements do:

    WITH CTE1 AS (SELECT TestColumn FROM dbo.TestTable),
    CTE2 AS (SELECT TestColumn FROM CTE1),
    CTE3 AS (SELECT TestColumn FROM CTE2)
    SELECT CTE3.TestColumn FROM CTE3
    INNER JOIN CTE2 ON CTE3.TestColumn = CTE2.TestColumn;

    In the final select clause, both CTE2 and CTE3 are flagged with 'Use alias for all table sources' (ST010).

    Seems a bit OTT to suggest references to CTEs are aliased? I accept that a CTE defines, in relational terms,…

    4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  19. Code Analysis EI028 Incorrectly Identified When Adding Not Null Column With Explicitly Defined Default Value

    Stop raising EI028 when adding columns using style:

    ALTER TABLE dbo.MyTable
    ADD TestColumnB CHAR(1) NOT NULL,
    CONSTRAINT DF_MyTable_TestColumnB DEFAULT ('B')
    FOR TestColumnB;

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
  20. Ability to code analyse existing database (SPs, triggers, etc.)

    SQL Prompt provides the ability to improve your on-the-fly coding according to standards and best practices defined locally or within the organisation.

    How about the ability to analyse an existing database and isolate problematic areas, code smells and provide not only recommendations but also the ability to refactor the database code based on rule-sets?

    This would be really great and a time-saver to improve the code quality in the whole database.

    Thanks, Jochen Kirstätter, MVP

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Code Analysis  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base