73 results found
-
Jumping to Begin and Jumping to END
Hello,
I try some Add ins for sql server and i found a very interesting and useful functionnality on Softtree sql assistant.
When we have a very large Stored procedure for example, with several BEGIN and END , softtree have a functionality when i place the mouse on BEGIN to [Jump to end] to find the corresponding END, the opposite is also true, when i Place the mouse on END [Jump to begginning].
This functionnlity is very very useful.
I hope you consider developing the same functionality in your SQL Prompt.Best regards,
Luis6 votes -
Insert Default Values should include default values defined on the table.
For example, if a table is defined as such :
CREATE TABLE dbo.T1 (
col1 INT DEFAULT 100,
col2 VARCHAR(100) DEFAULT 'Example',
col3 DATETIME DEFAULT '01/01/2019'
)And use auto-complete to generate and INSERT, it will produce :
INSERT INTO dbo.T1( col1, col2, col3 )
VALUES( 0 -- col1 - int
,'' -- col2 - varchar(100)
,GETDATE() -- col3 - datetime
)Instead, it would be nice to have it produce the insert with the defined table default's, something like :
INSERT INTO dbo.T1( col1, col2, col3 )
VALUES( 100 -- col1 - int
,'Example' -- col2 - varchar(100)
,'01/01/2019…5 votes -
Temporarily Elevate Exact Matches Over Recently Used Suggestions
I like the new feature to put recently-selected items at the top of the list for Intellisense. However, when I have typed an exact match, I would like to see Intellisense elevate that exact object to the top of the list.
For example, suppose I have recently selected a table named "dbo.OrderDetail", and suppose that there is another table in the same database called dbo.Order. With the new feature, I cannot access "dbo.Order" as the top candidate, because it is a partial match of "dbo.OrderDetail," and so SQLPrompt puts that name at the top.
In a nutshell, I would like…
6 votes -
Recently Used Suggestions
Love the Recently Used Suggestions feature. It's like it's reading my mind and is a definite time saver.
1 vote -
Recently Used Suggestions
Love the Recently Used Suggestions feature. It's like it's reading my mind and is a definite time saver.
1 vote -
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 -
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 -
When excluding schema / database from suggestions, if provide excluded schema, suggestions should still appear, but limited to that schema
So i specifically excluded our "temp" schema from my suggestions and it works brilliantly, however, when specifically want that schema, after completing the schema name it should show me the suggestion within that schema? -
Currently my options are to remove the "don't show suggestions" for the temp schema and then add it again after this session.2 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.7 votes -
Ignore SQL Snippets that match table alias
Sometimes SQL Prompt generates an alias that matches an existing snippet key. My suggestion would be to ignore snippets when it's an auto generated alias.
example:
select * from DataEnvironment de (where de is the automatic alias) becomes
select * from DataEnvironment DELETEIt's rather annoying :)
6 votes -
List aggregate functions before system fields
When putting a COUNT in a select field, the default option in intellisense is sysxmitbody.count. I understand if I have a field that contains the aggregate name in my table that you suggest it first, but I never want sysxmitbody.count - and if I do, I'd expect to go looking for it.
I feel like I've hit this problem with other aggregates as well, but can't find another example at the moment.
Not sure the best fix, maybe list all system tables after user tables and functions?
2 votes -
Autocomplete stored procedure using local time zone on datetime arguments.
When auto-completing an "EXEC storedProc" statement, SQL Prompt will generate the input arguments (and outputs) and generate sample values for the input arguments. If an input argument is of type datetime, SQL Prompt generates a string literal that is equivalent to current date and time in UTC. Please provide an option to either generate a string literal that is the current date and time in the local time zone.
1 vote -
Autocomplete stored procedure using local time zone on datetime arguments.
When auto-completing an "EXEC storedProc" statement, SQL Prompt will generate the input arguments (and outputs) and generate sample values for the input arguments. If an input argument is of type datetime, SQL Prompt generates a string literal that is equivalent to current date and time in UTC. Please provide an option to either generate a string literal that is the current date and time in the local time zone.
1 vote -
Control the behaviour of SQL Prompt insertion
I would like the ability to control how SQL Prompt completes my statements for me, this mostly becomes an issue with procedures with multiple optional parameters.
If I used sp_whoisactive as an example, there are multiple optional parameters but it is capable of running with no parameters at all, so I find myself having to spend longer than I want to either highlighting the bit I want execute or deleting all the parameters that just got written for me.
So a setting where I can assign keys to complete full statement and keys to simply complete object name would be…
1 vote -
1 vote
-
Autocomplete WHERE clauses with variables
It would be neat if WHERE clauses could get autocomplete suggestions with declared variables (or variables that are procedure parameters). Example:
Assume Table1 with one column Column1.
DECLARE @Column1
SELECT *
FROM Table1 T
WHERE T.Column1 = (suggest @Column1, any variable that exactly matches column by name, except @)2 votes -
SQL AUTO-SYNTAX
when you insert a ssf (Select * from) you select the table and correct automatically errors like WEHRE, WERE, WEHER where the user wants to say a WHERE a logical word dictionary in which, it could be done by matching characters if all the characters written are 100% or 90% matches with word WHERE whenever is the order of the characters then autochange the text for where, This also can be matched with other KEYWORDS of SQL
2 votes -
Code Analysis Disable Rule for specific cases
Hi,
it would be extremely useful to allow the user to disable a code analysis rule for specific cases and not just on a global scope.
E.g.
cast(cast(0 as binary) pops up the issue BP008 (CAST/CONVERT to var types without length) which my be correct for certain cases but not always.It would be very hand if I could tell the analyzer to not give any warning for this single line, perhaps by adding a pseudo comment like --##BP008 or similar.
This comment would temporarily disable the warning for this single line/case but not for the rest of a script.
…
15 votes -
Detect the database compatibility version
When using SQL server 2016 with a database that has it's compatibility level set to 2012, I'm still being offered auto complete options for 2016 features. e.g. string_split
SQL Prompt needs to detect the database compatibility level and adjust it's intellisense accordingly.
2 votes -
Discover metadata for OPENQUERY
When I use the OPENQUERY syntax to retrieve data across servers, SQL Prompt does not discover the metadata (column names, data types, etc.) of the fields returned.
My suggestion is that you add support within SQL Prompt to make metadata for fields retrieved by OPENQUERY available just like you do for linked servers.
7 votes
- Don't see your idea?