701 results found
-
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 -
Is there a way to run your code analysis rules against an existing database?
To help our developers we - as dba's - perform validation against their procedures and database code. The library of rules that is incorporated in SQLPrompt could be a good rule of thumb for the basic stuff of reviewing, so that we can focus on other stuff when validating.
Is it possible to run the rules "engine" of SQLPrompt against an existing database without having to open the code manually?3 votes -
insert default default values should just use SQL Server defaults
When the option to insert a values clause with default values for an INSERT statement is in force, the default values used by SQL prompt ignore nulls. e..g if your table is CREATE TABLE foo (bar int NULL) and you let SQL Prompt build an INSERT with default values, it uses 0 as the default for column bar. This is wrong. The true default is NULL. It would be better if SQL Prompt just used a value clause like :
VALUES (DEFAULT)
and let SQL Server figure out the default. Worse yet, check out this table and the generated code:
…
3 votes -
Make parentheses rules customizable (where what applies) instead of a global setting
I have different wants for parentheses rules: Collapse short content or not, Having Parentheses on separat lines or leading the content, etc. It all depends on the context. But currently the setting is global.
I would like to be able to define one rule for, say, Primary Key definitions, and another rule for, say, the columns of a table.
I would want one thing for Control Flow sections, and another thing for Variables declarations.Today, I need to choose which one to be dominant (or stop using FORMAT SQL on the entire script, but just highlight the block where I…
3 votes -
auto complete set proc parameter defaults
when stored procedures have variables with defaults, your auto complete intellisense does not set the default. for example, if the parameter @a is an int = 5 in the creation of the proc, your auto complete says @a = 0 --int
3 votes -
Closing parenthesis and content indention on APPLY/EXISTS not indenting
It seems that the contents and closing parenthesis of EXISTS and APPLY clauses is not being indented as I would expect. So either i'm weird....or Format SQL is doing it wrong?
I'm using (
.....this parentheses style
)What it's doing:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
.....SELECT *
.....FROM tblB b
.....WHERE b.Col1 = a.Col1
..........AND b.Col2 = a.Col2
..........AND b.Col3 = a.Col3
)What I expect:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
..........SELECT *
..........FROM tblB b
..........WHERE b.Col1 = a.Col1
...............AND b.Col2 = a.Col2
...............AND…3 votes -
"drop user"
Highlight of today was when I ran
DROP USER MyUserIn 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?”
3 votes -
SQL Prompt Issue EI030 shows fals positive on views including TOP (n)
If a View looks like
SELECT TOP(n) FROM x ORDER BY x.clumn
SQL Prompt shows issue EI030 although the ORDER BY is vital for the TOP (n) clause3 votes -
Azure SQL Database Smart Rename support
Smart rename doesn't work on Azure SQL Database without creating a SQL login to use for the task. Be nice to support connections via Active Directory Password, or any of the other Azure AD auth options.
3 votes -
filter snippets between default and custom
Ability to easily identify user-created snippets from default Redgate snippets.
I love snippets and I create a ton of them, but there's no easy way for me to filter the list of snippets to see which ones I created vs the ones that shipped with the product. I'd love the ability to be able to filter the list of snippets to show my custom snippets so I can find them easily.
(My work around is just to use a naming convention that groups them all, but this feels inefficient because it requires that I type more letters to activate the…
3 votes -
Align BETWEEN with comparison operators
It's currently possible to align operations in WHERE which is great, but BETWEEN is not aligned.
Example - currently:
WHEREModifiedDate BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
AND City__________= 'Bothell'
OR LEFT(PostalCode, 2)= 'CB'
OR PostalCode_______= @prefix + @suffixExpected:
Example - currently:
WHEREModifiedDate_BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
AND City________= 'Bothell'
OR LEFT(PostalCode, 2)= 'CB'
OR PostalCode_______= @prefix + @suffix3 votes -
Copy a row selection and format into a into a 2 column output (column, value)
I would like to see the ability to copy a selected row or a number of cells in a grid, and add it to the clipboard as a transposed view of the record
with 2 columns (Column Name, Value) to allow results to be easily pasted into emails etcexample (simple result only the result values would need to be selected)
ID Name Activation Date
1234 John Smith 2018-01-14output on clipboard
ID 1234
Name John Smith
Activation Date 2018-01-043 votes -
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.
3 votes -
Add formatting support for OFFSET and FETCH NEXT
The Format SQL command currently overlooks these keywords and they end up appended to the last line of the ORDER BY clause. Ideally, I'd like to have the option to place both OFFSET and FETCH NEXT on separate lines, aligned just like the SELECT, FROM, WHERE, and ORDER BY keywords.
3 votes -
Don't allow for aliases that match snippet acronyms
What I sometimes run into, is that a table gets an alias (by SQL prompt), that matches an acronym for a snippet. Then, whenever I'm writing out my query, while calling the table by alias, snippet manager replaces the alias with the full snippet. Which can be annoying as Ctrl-Z doesn't work.
My suggestion would be to check the snippet manager before assigning aliases and not have them overlap.
Thanks.3 votes -
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 )3 votes
- Don't see your idea?