73 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
remove table names (that are not in any joins) from where clause suggestions, or at least deprioritize it.
It keeps suggesting table names dbo.Something when writing the where clause even if the table is not in any join clauses. This is a pain as I keep selecting the table instead of the column if the names are similar.
1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
MS_Description supporting hyperlink when SQL Prompt is showing the tooltip
I'm currently working on a database with some really complex calculations which are saved then in a table. Putting these formula in the MSDescription is a pain as it cannot be shown correctly in the appearing tooltip text.
A nice Feature would be that I'm able to add a Hyperlink in the MSDescription which is pointing to the document in our SharePoint Server (or Wiki or whereever...).
Or - if this is not working, would it be possible to define a Special RedGate Attribute/Property (e.g. MSDescriptionRedGate) below the MSDescription which is containing a hyperllink and this…4 votes -
Use icon to denote fields with indexes
When the drop down appears with field names (like when you're typing in a WHERE clause), include a little icon for each field that's the first field in an index (like the key pic when it's the PK).
Being able to say "oh, that one has an index" would help me when trying to figure out how I want to filter things. (aka use "insertedtime" vs "posttime" vs the "start_time"). I'd say to use one icon (maybe greyed out) for non-clustered, and a different (or not greyed-out) icon for the clustered. You already include the field size, so…
16 votes
- Don't see your idea?