663 results found
-
When typing between tics ' Intellisense is not needed.
at some point i noticed it started recommending suggestions when typing between ''. this should be a literal string with no suggestions required
2 votes -
Correct Inaccurate suggestions for auto complete of column name
Intellisense brings up 'd', CREATE SQL Server login, to top of suggestions when referencing a column beginning with 'cl'.
Specifically, I see this in the where criteria. Have no clue why it would even bring up a 'CREATE SQL Server login' snippet in the context of a WHERE; especially when the autocomplete is coming from the dot to an alias of the table.1 vote -
Parentheses
New Parentheses Style - #6 but ends like #1
Numbering starting at the top left as #1 and continuing to the right one as #5. With the next line starting as #6 and finishing on the right of line 2 as #9.
In the global parentheses settings, Lets make a #10 option which works like #6 in all ways except the closing parentheses is aligned with the beginning parentheses like it does on #1. Actually looking at the graphic that shows on #1, this looks like what I want, the trailing parentheses is below the first one, but #1 has…1 vote -
Open Transaction Warning
Occasionally, developers working in SSMS accidentally leave transactions open. This causes big issues, of course. SSMS lets the user know if they try to close a tab with an uncommitted transaction, but only when the user tries to close the tab.
I would like a feature in SQL Prompt so that it lets the user know that they have an uncommitted transaction. SQL Prompt could prompt the user via a toast pop-up or coloring the connection tab or something
28 votes -
Add Remove Comments to Context Menu
I love the 'Remove Comments' feature, however it takes too many clicks to implement. Please add it to the context menu.
1 vote -
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 -
Highlight difference between selected rows
Time to time you need to compare data in the rows, for example when looking for the cause of duplication. If the query is complex enough with joins and wide tables I usually run
SELECT * FROM ...
and check where the duplication begins to easily find the root cause. The easiest way for me to do so is to copy it into the excel and do some simple formula to find the exact columns that have difference.
It would be nice if SQL Prompt would support that feature. If it's possible then it can be done by highlighting needed…
2 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 -
Please allow CASE statements to start on their own line, preferably indented from the line before.
Please allow CASE statements to start on their own line, preferably indented from the line before, rather than starting way, way off to the right when there's a significant amount of stuff before them. Nested CASE statements are nearly unreadable when they're so far off the screen, for complex or nested statements.
This is a pretty simple example, but I've got real ones where the WHEN is so far over I can't even tell it's there without scrolling.
SELECT
CASE
WHEN @SPID = 3 THEN 'th'
WHEN @spid = 88 THEN 'bobasdlkfjalk;sdfjalks;djfla;skjfdlkasfjlks' + CASE
WHEN @SERVERNAME = 'bb' THEN 'a'…6 votes -
Post execution
Automate a task after a query execution.
Like, after execute a long query, send-me a email, or if the query run from a long time do something or start a job, another query, kill the original query.
Be able to enable this trigger after start a query will be nice too.1 vote -
Add space between closing parethesis of a function call and FROM
Add an option to add a space between a function call, such as COUNT(), and FROM so that we don't end up with code like SELECT COUNT()FROM table. That doesn't happen when I select "Add spaces around parentheses" in the global parentheses options. The only way I've been able to get SQL Prompt to preserve that space is to select "Add spaces around parentheses" in the Function calls options, but I don't want a space between the function name and opening parenthesis.
4 votes -
Can we have a keyboard shortcut for "Script Object as ALTER"?
Can we have a keyboard shortcut for "Script Object as ALTER"? You had it before but it isn't available with the latest version.
2 votes -
RedGate In Clause
When redgate is writing the "in clause" for us based on selected cells it would be nice if it also put the column name in the clipboard when all fields selected are from the same column,
1 vote -
Implement all of the Find Unused Variables and Parameters functionality in Code Analysis
Currently Code Analysis does not implement all of the items that Find Unused Variables and Parameters does.
Specifically I know it's missing:
- Declared variables that are used before a value is assigned
- Assigned values that are never usedEx.
With this code:DECLARE @Test NVARCHAR(1)
DECLARE @Test2 INT
DECLARE @Test3 DATESET @Test = 1
SET @Test = N'Test' + @Test2
Code Analysis will flag the DECLARE for @Test for having a NVARCHAR of size 1 and @Test3 for not being used, but it will not flag @Test2 for being used before a value is assigned to it…
6 votes -
conditions new line after
Currently we have a standard of placing new line before and after conditions with indent accordingly such that:
a=1
AND
b=2Current version only does:
a=1
AND b=2This is pretty much the only thing lacking from being able to just auto format all our procedures with a single click.
4 votes -
Support SSDT for SQL Prompt
Create Install Package for installing SQL Prompt in SSDT. SSDT is a VS shell, so Prompt should be easily incorporated.
5 votes -
COPY AS ALTER BUTTON
Hello,
So I love the suggestion feature where I'm able to type in an object and the code appears to copy. Home run with this feature I can't thank you enough for it.
I was wondering if it would be possible to expand on it though.
Here is a sample. I'm looking to alter an object, let's say a stored proc...
I usually begin by typing EXEC <name> to trigger the suggestion for stored procs to give me the object.Once the suggestion finds the object, the script contents appears in a side window.
Using the COPY button in the…
1 vote -
inserting table adds database name
When you select a table from the intellisense list
Precede the table name with the database name as well
Currently it is only inserting the schema name in front of the table name
i.e. dbo.<table name>It should be <database name>.<schema name>.<table name>
2 votes -
Make the Issues List more useful - Rule Disable, Specific Help, Hide Issue in List
The list is useful to drive code positioning, but that's all it does. Rules like ST011 that go against authoritative SQLPass presentations are noise. Yes, we can click the SQP Menu, nav to manage, scroll down, and finally disable, save, then refresh... (out of breath!). Just right-click and Disable rule, which also refreshes the list. That kind of useful RC-Menu. And instead of having to go to the Rule Maint to see exactly what the rule is enforcing, RC-menu has "Show Issue Help" in a bubble, built in. And for those cases where a rule isn't to be shut down,…
4 votes -
Provide support for "Suffixes to ignore" in "Insert code > Aliasing" options
We use a data warehousing strategy that creates potentially dozens of tables for multi-class entities in the data warehouse, so we have many tables that end in "core". This leads SQL Prompt to alias the object with a final "C" that we then remove manually. For example, our InstanceCore and Database_Core tables are aliased to "IC" and "DC" when we would prefer "I" and "D" respectively.
Can SQL Prompt's Aliasing capabilities be extended to support "Suffixes to ignore" just like the existing "Prefixes to ignore"?
1 vote
- Don't see your idea?