- or
No existing idea results
- ~ No ideas found ~
702 results found
-
Script as Insert - Floats end up with innacurate data precision
After running a select on a table with a float(53) column, "Script as INSERT" from the right click menu on the results will script an insert with float(8) as the data type instead of float(53), presumably from the length of the column being recorded as 8 bytes when the float(n) is defined with n being bits.
Minor thing, but ended up causing issues with an equal statement since the floats had different precision when comparing to the original table.
1 vote -
Export settings doesn't export snippets
When I export my settings, my own snippets are not exported.
4 votes -
Copy selected the column headers
After running a select statement, I want to be able to copy selected column headers without copying any data.
2 votes -
Fix the confusing multiple usage of your company name
You should fix the use of multiple versions of your name (Red Gate | Red-Gate | Redgate | redgate | red-gate) across all software and communications. See attached picture.
We try to promote your products in our consulting company, but everyone uses a different name to refer to your company.
4 votes -
Fix the confusing multiple usage of your company name
You should fix the use of multiple versions of your name (Red Gate | Red-Gate | Redgate | redgate | red-gate) across all software and communications. See attached picture.
We try to promote your products in our consulting company, but everyone uses a different name to refer to your company.
1 vote -
Allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting
SQL Prompt should allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting.
Single line comments are a pain when tuning queries. I would always use block comments in my code except when I don't want SQL Prompt to not mess with certain T-SQL it does not format to my standards.
Blocking formatting should support both type of comments.
/* SQL Prompt formatting off */
-- SQL Prompt formatting off9 votes -
Add SQL Prompt to the Mac / Linux version of Azure data studio
I see that Azure data studio support is on the roadmap, but cannot see any reference to the MacOS / Linux versions of Azure data studio?
Would be great to not have to boot up Windows to get to the awesome speed and power which SQL Prompt provides.133 votes -
Ability to exclude certain objects (Procedures/Functions/Files...etc.) from being processed for a rule
Currently there is no way to tell Code Analysis to ignore this specific object for a specific rule which has led to several false positives and wasted time re-investigating how to address the issue in the object only to come to the same conclusion as before that this is one of the rare cases where breaking that rule is ok.
My example is we have one stored procedure out of a thousand where the use of a NVARCHAR(2) makes sense and is actually more efficient then switching to a NCHAR(2) for what the code needs to do. Unfortunately the procedure is always flagged for violating BP009 - Avoid var types of length 1 or 2. And so every time a junior dev goes to work on the procedure they spend hours trying to remove the NVARCHAR(2) and replace it with a NCHAR(2) only to find out after a review with a senior that they wasted their time as this is the one case where it's ok.
What I would like to see is on each rule be able to specify the name of a object that should be excluded for that rule.
I know that this feature used to exist at one point for some of the rules because looking at the Code Analysis xml shows possible entries for it, but there's no graphical way to do it anymore and no documentation on how to set those items up in the xml.
Currently there is no way to tell Code Analysis to ignore this specific object for a specific rule which has led to several false positives and wasted time re-investigating how to address the issue in the object only to come to the same conclusion as before that this is one of the rare cases where breaking that rule is ok.
My example is we have one stored procedure out of a thousand where the use of a NVARCHAR(2) makes sense and is actually more efficient then switching to a NCHAR(2) for what the code needs to do. Unfortunately the procedure…
4 votes -
SQL Prompt Support for Azure Synapse (Azure SQL Data Warehouse)
Please add support for
SQL Prompt Support for Azure Synapse (Azure SQL Data Warehouse)51 votes -
"Script as INSERT" should refer to current table instead of a temp table
"Script as INSERT" creates an INSERT script with a tempt table, but instead it should script the current used table.
In that way you can easily write scripts to synchronize your data between different environments.
Thank you2 votes -
Draw line from begin to end of different colors
It would be nice to have colored lines that visually enhance the start / end of a while / if statement
4 votes -
Suggest data truncation
Consider I've got a variable of varchar(35)
I perform an update on a column of varchar(10), it should suggest that there will be a truncation
2 votes -
Follow the Visual Studio Theme
I'm running a dark theme in visual studio. When the suggestions pop up they are very bright.
5 votes -
"Insert Semicolons" feature should add Semicolon after "BEGIN"
When using a BEGIN/END block, the "Insert Semicolons" feature adds a semicolon after "END" command, but not after the "BEGIN" command.
One reason why this should be done, is the use of the THROW statement, which requires the previous statement to be terminated with a semicolon.
Technically it is still runnable code, but, SSMS (as of version 18.8) sees it as a syntax error (see screenshot).
I don't know which is the appropriate fix...waiting for SSMS to fix the syntax error it shows (but I doubt they will since the non-use of semicolons is deprecated), or if it's appropriate for this feature to add them after BEGIN statements.
Sample:
BEGIN
THROW 51000, 'Test', 1;
END;When using a BEGIN/END block, the "Insert Semicolons" feature adds a semicolon after "END" command, but not after the "BEGIN" command.
One reason why this should be done, is the use of the THROW statement, which requires the previous statement to be terminated with a semicolon.
Technically it is still runnable code, but, SSMS (as of version 18.8) sees it as a syntax error (see screenshot).
I don't know which is the appropriate fix...waiting for SSMS to fix the syntax error it shows (but I doubt they will since the non-use of semicolons is deprecated), or if it's appropriate for…
3 votes -
Separate ALIAS Alignment - table vs. column
Aligning based on column-alias makes for much better readability. When turned OFF, because some long-named table's alias pushes the TABLE-alias way to the right, all other table aliases follow it...into the NON-VISIBLE area (when using multiple vertical tabs).
Please SEPARATE these into TWO options:
. Align Column Aliases - on/off
. Align Table Aliases - on/offTHERE IS A BUG TO FIX HERE TOO: If a UDF is bounded by "--SQL Prompt formatting off/on" the TABLE ALIAS position REMAINS as if the UDF's alias was in it's SQL Prompt position, NOT where the excluded code has it! NASTY.
You could also FIX the NON-ALIGNMENT of UPDATE...SET...Column lists...
Thanks
Aligning based on column-alias makes for much better readability. When turned OFF, because some long-named table's alias pushes the TABLE-alias way to the right, all other table aliases follow it...into the NON-VISIBLE area (when using multiple vertical tabs).
Please SEPARATE these into TWO options:
. Align Column Aliases - on/off
. Align Table Aliases - on/offTHERE IS A BUG TO FIX HERE TOO: If a UDF is bounded by "--SQL Prompt formatting off/on" the TABLE ALIAS position REMAINS as if the UDF's alias was in it's SQL Prompt position, NOT where the excluded code has it! NASTY.
You could…
6 votes -
Separate UDF Formating from Built-in in "Function Calls"
We cannot treat UDF parameter listing/indentation in similar vein to Stored Procedure call formatting. All "Functions", be they UDF or built-in, are lumped into the same four RESTRICTIVE options on the "Function calls" page, and we have no "parentheses style" options for them.
We need:
1. Separation by type (UDF vs. Built-in).
2. Global ==> Parentheses, to apply to UDFs, by our choice.Thanks.
1 vote -
Tab history remove duplicates scripts
Have the ability to delete duplicate scripts in the Tab History. Example I may open a stored procedure to look at it or modify then close and then it is stored in the Tab History as Closed. But then in a few days or so I open the same store procedure and do the same thing it is now in the Tab History also. I have made no changes to either day it is open then closed but, it's in the Tab History twice. Now think about this over a few months. That Tab History grows with duplicate scripts.
16 votes -
Ability to make/see notes about servers
It would be very handy if there was a way when you open a server in Object Explorer that it pops up with notes about that server. For instance, there is a job we have on EVERY server in our environment except one random server that no one hardly thinks about. But if that job is there, then it messes up things. It would be great if when anyone on our team who has redgate sql prompt opens that server they get a reminder that we add on there that says some special note (in this case “DO NOT ADD AP Job!!!”). It could even be stored in like the extended properties for the server and SQL Prompt just reads that first when it’s opened. An optional feature on top of that, would be anytime you open that server as a new query window. I’d say optional, because some people may not want to see that everytime. But that would help as well when people want to see notes, but they never use the GUI and just write out all their code.
It would be very handy if there was a way when you open a server in Object Explorer that it pops up with notes about that server. For instance, there is a job we have on EVERY server in our environment except one random server that no one hardly thinks about. But if that job is there, then it messes up things. It would be great if when anyone on our team who has redgate sql prompt opens that server they get a reminder that we add on there that says some special note (in this case “DO NOT ADD…
2 votes -
Do not auto complete literal strings
Currently SQL Prompt displays suggestions for auto-completing literal strings. These are never valid suggestions so can this be turned off (or at least have an option to turn this off)?
3 votes -
Find invalid objects in multiple databases
Please could you add an option to check for invalid objects in multiple databases and to be able to export the results in either a single file or 1 per database. It's a real pain doing 1 at a time and manually selecting the results to do a copy/paste.
4 votes
- Don't see your idea?