663 results found
-
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 -
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 -
code folding
Enabled Intellisense conflicts with SQL Prompt and needs to be disabled. This also disables Code Folding feature (Outline Statements) of SSMS, which is very useful for large coding projects.
It would be helpful if SQL Prompt were to offer the similar feature.8 votes -
Aggrigate column name as
When writing SQL codes I frequently use aggregate functions such as Sum, count, avg etc.
When writing for exapmle sum(SalesVolume) it would be nice to have an autocomplete option to Sum(SalesVolume) As SalesVolume or Sum(SalesVolume) as SumSalesVolume.2 votes -
Add "duplicate a line" feature similar to Resharper's Ctrl+L.
When cursor is placed on any line simple shortcut would insert exactly same line below and move cursor to the newly inserted. No prior selection of any kind necessary.
1 vote -
1 vote
-
format Window functions
SQL Prompt fails badly in formatting window functions. As these are present at least since SQL 2014, SQL Prompt should be able to interpret them and format them accordingly.
Example:
I would format the LAG() function as follows:
SELECT
myColumn AS realColumn
,LAG(myColumn, 1, 0)
OVER (
PARTITION BY someColumn
ORDER BY anotherColumn) AS calculatedColumnTry this with SQL Prompt - it's result is not very nice...
5 votes -
Add option to ignore is_ms_shipped flag in suggestion list
When typing a snippet eg I type zcod I get 3 suggestions - but the top one is a merge replication conflict table definition for MSmergeConflictZZZFULLZZZcodt and the 2 below it are my own snippets starting with zcod
I don't understand why this is the case, my own suggestions that START with zcod should take precedence over an isms_shipped table that ends in zcod surely.
I see you recently added (I am on 9.5.11) ordering based on frequency and I never click this table as it serves no purpose so I cannot understand the behaviour.2 votes -
PE006 is Too Noisy for Temp table Parallel INSERT
We use the WITH (TABLOCK) hint extensively for loading temp tables - see https://www.sqlshack.com/use-parallel-insert-sql-server-2016-improve-query-performance/
PE006 is far too picky - it yells at every such statement in our high-volume hybrid solution. It would be good to "silence" this kind of rule-breakage so we can see any REAL violations on persisted tables.
Please augment to utterly ignore temp tables.
1 vote
- Don't see your idea?