689 results found
-
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 -
SQL Prompt Code Visualization (Like Flow Chart)
SQL Prompt should be able to Visualize the Code and represent the code like Flow Chart.
This Feature will be very useful while working with heavy Stored Procedures.The Sample Code Visualization image is shared below:
https://drive.google.com/file/d/1dE0H7UP1MOuOZ4A3e4urUkDlR0FD4474/view?usp=sharing
21 votes -
Add option to wrap lines when concatenating strings
Sometimes I set a variable equal to many strings concatenated together using the "+" syntax. When I format with Regdate, there is no option to wrap lines in this case. Everything ends up on the same line as the SET, so the lines often get very wide and go off screen.
It would be great if there was an option to wrap text if things got too wide horizontally.
One solution would be a setting to format concatenated strings like this:
SET @Variable = N'String1'
+ N'String2'
+ N'String3'4 votesHi Amanda,
Would the ‘wrap lines longer than X characters’ option in the formatting styles help with this?
Tim
-
Add context menu shortcuts to SQL Prompt context menu entries
I want to be able to quickly switch between active styles.
I'm informed that the solution to this was to add the Active Styles section of the context menu, to allow quick access to the active styles.
That's fine as far as it goes, but that entry is very far down the menu and is only quickly accessible by mouse.I would like to suggest having the "Active Styles" entry changed to "&Active Styles" so that the A becomes a shortcut in the context menu; and to have each of the styles listed as &1, &2, &3 etc. in the…
1 vote -
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 -
Run Script at Cursor
Run Script at Cursor just Oracle SQL Developer with F5 or Alt+X. Please implement this very helpful functionality.
1 vote -
COLUMNPROPERTY
COLUMNPROPERTY (https://docs.microsoft.com/en-us/sql/t-sql/functions/columnproperty-transact-sql) is missing two suggested property values that were introduced along with System-Versioned tables in SQL Server 2016.
Please find the missing values below:
GeneratedAlwaysType
IsHidden1 vote -
Allow Copy/Paste contents of 'List of Code Analysis Issues' window.
Sometimes I would like to just copy/paste the issues discovered and include in an email. Currently, I cannot copy the Issues list. It takes too much time/effort to export to a file and then attach that file to an email. Copy/paste would be so much easier.
2 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 -
add trigger definition to a triggers tab on object definition box
Currently, when hovering over table objects, and clicking on the table name mini popup, you get the object definition box, with a 'Script' and 'Summary' tab.
The 'Script' tab has the table and index creation scripts, and the 'Summary' tab lists the column definitions.
For tables with triggers, it would be nice to have a 'Triggers' tab that contains
any trigger scripts for the table.1 vote -
Top with parenthesis should be a formatting option
Changing
SELECT TOP 10...
to
SELECT TOP (10)... should be a formatting option.
11 votes -
Allow query results to be editable grid
I would like to have the ability when using Redgate to develop a query as I do today in a new query window with all the object search and suggestions features currently offered in your product.
After I get the query returning the correct record set, I want to be able to edit the record set without having to copy the query and navigate to SSMS’s “Edit Top XXX Rows” menu item.
Editing a field on the row would update that field on that row when I move off the row.2 votes -
Make warning settings environment-specific
Hi RedGate Folks,
I think it would be helpful if the execution warnings settings were environment-specific. I.e., in the color coding section, we can establish which connections are prod, test, dev, etc. It would be great if I could -- for instance -- turn on warnings for DROP statements in my prod environment only.
2 votes -
Include auto fix for single quote string literals as aliases warning, Issue code: DEP01.
Create auto fix for Issue code: DEP01 non-standard column aliases because of single quote delimiter. Also need to update SQL Format tool, it is currently using single quote and there is no way I could find to switch it to double quote.
2 votes -
Improve Autocomple
After Update to 10.0.
When you for example press J for join and confirm this input with Tab, it wont add a Space. You have to add this space manually :(
maybe it is possible to add automatily always the space1 vote -
Refactor Select Into Statement as Create and Insert
I would like an efficient way to refactor this kind of statement...
SELECT ID, Name, Job INTO #Employee FROM Employees
into something like this-
CREATE TABLE #Employee (ID int, Name varchar(max), Job varchar(max))
INSERT INTO #Employee
SELECT ID, Name, Job
FROM EmployeesThe PE003 rule keeps triggering on these statements but it takes an annoyingly long time to write out the column definitions by hand for longer tables.
2 votes -
Move caret within python_case_identifiers similar to CamelCase
Similar to the movement of caret within CamelCase, could you please enable such behavior for pythoncaseidentifiers? I'd like the caret to stop in these places when using CTRL+<right or left arrow>: (1)python(2)case(3)identifier. Would that be possible, please?
1 vote -
Feature to make variable declarations persistent while testing
Allows you to define (on a per tab/session basis) a list of variables you would like to be declared before running the highlighted piece of SQL.
Reason: I like to put all of my "magic numbers" in variables at the top of the proc. This works great for code readability, but it's a pain to troubleshoot because now everywhere the variable is used, you need to copy that variable declaration above whatever code you are testing in order for it to work.
4 votesThanks for the suggestion Chad. We think this is a nice idea, we’ll wait to see how others in the community comment and vote before taking it forward.
Tim
-
Only load suggestion for fresh new databases
Do you think it's possible to only have the refresh of suggestions the first time a database is loaded (so skip refresh if the cache already exists, but let the possibility to manually refresh cache for this db with the contextual menu of course)
We have hundred of databases (with thousands of view and sp) and sql prompt try to refresh all the time the same databases (for example when we restart Management Studio) and nothing never change in these databases ...
So we would like to load schema automatically only the very first time and then on demand.
Thanks
1 vote -
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
- Don't see your idea?