689 results found
-
Custom Rank Suggestions
Could see there are ranked suggestions, which is good.
Can we take this to next level by letting user add custom ranking to suggestions to see those we rank always at the top but with a requirement that you need to enter at least a single letter so that your custom suggestions starting with that letter would be the first in order of display.Thanks!
3 votes -
Format SQL Backup to URL with credential breaks code
Formatting a SQL batch which contains
BACKUP DATABASE Databasename
TO URL = N'URL'
WITH CREDENTIAL = N'Credential'leads to
BACKUP DATABASE Databasename
TO URL = N'URL'
WITH AS CREDENTIAL = N'Credential'the AS between with and credential is wrong.
Please fix :-)
3 votes -
Remove PE019 (Consider using EXISTS instead of IN), or allow it to be disabled
Following the suggestions of rule PE019 (Consider using EXISTS instead of IN) leads to performance issues, by creating correlated subqueries. Even the documentation of the rule admits that there is no longer a performance benefit of doing what is suggested. Please remove the rule or allow the rule to be disabled across a team. At the moment, the disabling of rules is done per developer, and a developer who did not know to switch off this rule, followed the advice, creating a performance problem.
3 votes -
CTE column list formatted like the columns in the AS list
The columns listed in the CTE are not formatted like the columns in the AS clause. On larger CTE's, the listed columns may be hundreds or characters long so we get
with xx
( a, b, c, d, e, ...) AS
(Select a,
b,
c,
d,
e,
...3 votes -
Add option to check if object exists when creating stored procedure
It would be helpful if you would add an option to check if the objects used in a stored procedure really exist when creating it.
Example:CREATE OR ALTER PROCEDURE [dbo] [SelectFromTableThatDoesNotExist].
AS
BEGIN
SELECT * FROM [dbo] [NonExistingTable];
ENDThe table used in the procedure does not exist, but the procedure can be created without errors. In this case, it would be desirable if SQL Prompt had an option to output an error when creating the procedure.
3 votes -
auto alias for colums name
when i join 2 tables with columns having same name sql raise the error 'Ambiguous column name'. if it possible i think it is usefull to have an auto alias generator. example:
select a.name, b.name from a join b => select a.name as aname, b.name as bname3 votes -
Code Analysis Selection Background Colour
Could we have the ability to change the background colour when Code Analysis detects an issue with the code. My scheme is black background and light coloured fonts. When code analysis detects an issue, the code becomes unreadable. Below has an example:
https://forum.red-gate.com/discussion/86480/code-analysis-selection-background-colour#latest
3 votes -
Indentation of clauses following alter table
Indent the clauses that may follow an alter table statement. They currently are on the same line or split but not indented.
3 votes -
Whitespace: Tab to indent, then spaces for alignments
Whitespace: I picked up an indenting/alignment pattern from a Stack Overflow thread that solves an abundance of arguments: Please provide the option for using Tabs to indent the line, and then use spaces for alignments following the first character.
3 votes -
Autofix : SC002 – Script should end with empty line
SQL prompt currently removes the empty line at the bottom of a script, which then break rule SC002.
Can format include a setting to add a blank line at the bottom of a script, and also autofix sc002 issues.
3 votes -
Option For Aliases (Only For Custon Alias)
Hi
it is better to SQL prompt use only aliases define with user.need option in Aliases : Only For Custom Aliases
Sorry For My Bad English
3 votes -
Show synonym script on F12
I would like to see the Script Object as Alter (F12) feature to work with synonyms. However, I am aware that a synonym cannot be altered - instead I suggest to generate a script containing a DROP and a CREATE statement.
That way one could bring up the code of the referenced object by selecting the synonym, pressing F12, selecting the referenced object and pressing F12 again.
3 votes -
Remove/replace String Literals
When you code a SELECT statement as:
SELECT EffDt AS 'EffectiveDate'
SQL PROMPT advises that string literals as column aliases have been deprecated.
Have an option to convert string literals, similar to Remove Square Brackets. In this case, Convert Column Aliases would either remove the apostrophes, where appropriate, or add square brackets if required (e.g. the alias contained special characters, a space or reserved word).3 votes -
Writing text within quotes
When typing a string of text within a quote, do not replace my text with objects from the database.
3 votes -
Display intellisense for view columns from underlying base tables
When working with views, you lose the intellisense for columns. It would be nice if SQL Prompt could get the MS_Description value for the view column from the underlying base table for the view.
3 votes -
Generate a meaningful filename when clicking 'Save' in SSMS
When you open up new queries in SSMS they are always called SQLQuery1.sql , SQLQuery2.sql etc. etc.
what would be useful is if SQL prompt generates a more useful filename when you click Save or Save As in SSMS.
For example,
Say I had the script:
CREATE VIEW report.vwRandomName
as
SELECT *
FROM TableAwhen I clicked save, it would replace SQLQuery1.sql with
report.vw_RandomName.View.Create.sql
and the same with other object types (table/stored procs etc) and other actions (create / alter / drop).
thanks
ben3 votes -
Ignore Begin statements with CTE immediately after
SQL Prompt's "Insert semicolon" function behaves weirdly when a CTE is a the start of a control loop. For example, if I have this code:
IF (1=1) BEGIN
WITH numbers AS (
SELECT 1 AS num
UNION SELECT 2
UNION SELECT 3
UNION SELECT 4
)
SELECT * FROM numbers
END;SQL Prompt will format it as
IF (1=1) BEGIN;
WITH numbers AS (
SELECT 1 AS num
UNION SELECT 2
UNION SELECT 3
UNION SELECT 4
)
SELECT * FROM numbers;
END;While the code runs, I think the semicolon after "BEGIN" makes very little sense. First, the beginning…
3 votes -
Give option to completely disable update prompts
The updates for SQL Prompt have gotten out of hand - almost every day when logging into management studio it will prompt users to install a new update. And the notification steals focus from the main window, so it interrupts workflow. Not to mention redgate recently deployed an update that completely broke SQL Prompt in SSMS 18.1 for anyone that installed it. Users should have the ability to disable the notification completely if they so desire - "skip this version" does basically nothing when a new version is released a day later.
3 votes -
too much prompting for upgrades
I'm constantly opening new SSMS windows, closing new ones, opening new visual studio windows, etc, and every time I open a new window, I have to acknowledge the upgrade prompt because it covers important parts of the window (like the status bar). Even if I select "next month" or "skip this version" I have to do the same for every new window I open since new sessions don't check for this option on existing sessions. SQL prompt is constantly getting updates (almost weekly, it seems), so i just start a new round of "skip this version" the following week.
Can…
3 votes -
compare datatypes in stored procedure calls with defined variables
When I call a stored procedure, I want SQL Prompt's code analysis rules to be able to tell me if the variables I am passing to the stored procedure are OK.
For example, if I pass a bigint variable to a SP that has a tinyint input parameter, I want SQL prompt to flag that as a potential issue.
Similarly, if I am passing a string variable defined locally as nvarchar(150) to a SP that takes only nvarchar(100), it should be flagged as an issue (because I am passing a string that may not "fit" into the input parameter).
3 votes
- Don't see your idea?