674 results found
-
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 -
Provide optional colors for Warnings & Highlighting > highlighting
Options, Warnings & Highlighting, Highlighting. The light gray does not work well on a black background. I'd like to be able to select another color for that feature.
2 votes -
Custom values for VALUES clause
I write a LOT of unit tests, usually at the rate of 15:1 to 20:1 to my executing code. I have these standardized and templated to make them easier and more consistent to build. e.g. @GUID UNIQUEIDENTIFIER = NEWID(),
@Char CHAR(1) = 'A',
@Int INT = 1,
@Datetime DATETIME = CURRENTTIMESTAMP,
@Decimal DECIMAL(18,10) = 1.0,
@Date DATE = CURRENTTIMESTAMP,
@Time TIME = CURRENT_TIMESTAMP,
@Bit BIT = 1,
@Money MONEY = 1.00,
@Binary VARBINARY(18) = 0x01,These go into my VALUES clause for INSERT statements, but I current have to do all of this manually, which takes a LOT…
2 votes -
"Remove Square Brackets" option
The "Remove Square Brackets" option does not work for "CREATE EXTERNAL TABLE" statement.
Please try this option with the example below and nothing happens.
CREATE EXTERNAL TABLE [ft].[Account]
(
[AccountId] [bigint] NOT NULL,
[AccountType] [nvarchar] (50) COLLATE NOT NULL,
[AccountCreatedDate] [datetime2] NOT NULL
)
WITH
(
DATASOURCE = FinancialDB,
SCHEMANAME = 'Account',
OBJECT_NAME = 'Account'
);2 votes -
Create a table variable from a table
Very often I need to create a temp table, table variable, or UDTT that is a duplicate or subset of an existing table. I'd like the @table definition to include primary key and unique constraints and any check constraints and default constraints that are in the actual table. No foreign key constraints obviously. SSMS object scripting botches this up by creating a bunch of alter statements instead of including constraints inside the CREATE statement.
7 votes -
Conditional Snippets - Either...logic in the snippet, or logic to decide which snippet to run
I have some snippets that I would like to be server specific. For example, we have two servers, each one has a sort of "support" database, but they do not have the same database name. But both databases have maintenance procs I like to use that do have the same name.
I'd like to have some way of saying "If I am on Server1, then run SnippetA, if I am on Server2 then run SnippetB"
OR
Allow something like this as part of the snippet:
$IF($SERVER$='Server1','String1','String2')$
3 votes -
Shift-F5: ignore other syntax errors
Current behaviour: let's say we're editing a multi-statement script. The cursor is in the middle of one of the statements. Some other statements in the script are broken (i.e. have invalid syntax) but the one under the cursor is perfectly valid. We hit Shift-F5, expecting the current statement to be executed. Instead, we get a syntax error on some other piece of the script half a mile down the screen.
Expected behavior: just run whatever is under the cursor and ignore all other parts of the script.
9 votes -
script insert as
Today’s mail from https://sqlquantumleap.com/2019/05/09/maximum-number-of-rows-for-the-table-value-constructor/
Shows as way around the 1000 rows limitation on the VALUES ()… statement.Please enhance SQL Prompts “Script as Insert” feature to use this method.
Currently SQL Prompt is scripting it like this, when the results window has more than 1000 rows:
CREATE TABLE #temptable( [id_user] int, [RowCnt] int, [mt] datetime)
INSERT INTO #temptable
VALUES
( 372, 2,N'2012-09-01T00:00:00')
INSERT INTO #temptable
VALUES
( 196, 2,N'2012-09-01T00:00:00')
INSERT INTO #temptable
VALUES
( 210, 2,N'2012-09-01T00:00:00')
…It can be done like this:
CREATE TABLE #temptable( [iduser] int, [RowCnt] int, [mt] datetime)
INSERT INTO #temptable
select *
from(
values…5 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
- Don't see your idea?