668 results found
-
Insert Snippet on New Query
Automatically insert a snippet as soon as you start a New Query in SSMS. I want all my developers to always start every script with a comment block with their username, date and a description of what the script is supposed to do. A shared snippet is already handy for this, but adding this could make it easier to build that habit for new team members.
2 votes -
Tie the SQL prompt Scripting to SSMS scripting
IN SSMS there is an entire list of scripting options (turn off/on collation, extended properties, etc). Can SQL Prompt read those options and format the scripts it generates based on those settings?
1 vote -
F12 to Create Table Script
F12 to Script views and stored procedures as ALTER is one of my favorite features. I would love it if F12 when I am on a table generates a CREATE TABLE script for that table.
2 votes -
Find invalid objects in script
Highlighting invalid objects is a nice feature, but it would also be nice to "find" invalid objects in a script.
Running SQL Format on a script with an invalid object in it runs fine and gives no error, it just doesn't prefix the object (like a table) with the schema.
It would be nice to have a quick and easy way to "go to next invalid object" or even for when you run SQL Format to have it bring up a warning saying "this/these object/s appear to be invalid".3 votes -
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 -
Stop OPENJSON after CROSS APPLY from showing up on new line
I have included a Sample SQL script. This script shows the desired formatting. I can't find any way to prevent the OPENJSON from being sent to a new line. For example:
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY OPENJSON(OJ.Value)
WITH (ID int) AS CAOJbecomes
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY
OPENJSON(OJ.Value)
WITH ( ID INT ) AS CAOJ2 votes -
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 off8 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.132 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…
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)48 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.
2 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…
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…
5 votes
- Don't see your idea?