292 results found
-
Higlight Case errors
Like Microsoft's IntellySense does, when you open or write a script, case errors in variable names, table names, and field names are underlined in red (higlight) as a warning and can be corrected if desired.
This funcionality is like a spell checker.
You currently open a script and SQLComplete is not able to tell you what case errors there are.
This is quite important in environments where this requirement is required to be met.1 vote -
Add context menu item "Copy to new window" to Results window
I often use SQL to generate SQL commands based on information from sys tables. This enables me to keep things in sync.
Currently I need to Ctrl-C my selection, open a new tab, Ctrl-V in it, and then hit F5.
A context menu item, that does all this (except F5) would be a nice addition.1 vote -
Persist column layout in Execution History
The execution history is a great feature. It can be made more using if SQL Complete was able to persist column changes (moves or exclusions). Currently, the end user is able to move the columns, for example, move the Server column to the left or right. The end user can also remove unwanted columns. However if you close SSMS and reopen, the columns are back to their original positions. This is not very user friendly as the purpose of a user changing the column layout is to have it displayed the way they want.
1 vote -
Show Est. row count in Table Tooltip at the TOP to avoid truncation
When hovering over a table name in the editor, show the Est. row count at the "top" of the tooltip rather than at the bottom, currently the tip runs off screen on tables with many columns, causing it to be invisible
1 vote -
Keep the comments when formatting procedures!
Keep the comments when formatting procedures! IT can't be that all comments are removed by the formatting process! That happens to my code when I execute ALTER PROCEDURE!
OR: Give me the option to NOT format my code! I use the Express Version.1 vote -
Use object name as filename for "script object as"
When using the menu option "script object as..."
1) when creating the new file have the name of the object be the filename. That way it is much easier to find in the tabs of SSMS instead of just another SQLqueryxx.sql file. This would make it much easier to find it again after switching away from that document.2) have some option setup to make it always be a create and not an alter. When I use the command its so I can see what the object is, I don't want to accidentally modify it so create means sql server…
1 vote -
Email notification when query completes
I previously used SSMSBoost. There was a feature, Query Post-Execution Handlers, that included Results per Email as an option. This feature leveraged PowerShell as the engine, perhaps because it was a Windows installation, and a "script generator" dialog box that converted selected options and variables into a PowerShell script and email message. I would have added a screen capture of this interface, but this post won't accept attachments. The feature also accepted a threshold so it would only apply to queries that exceed a specified number of seconds. It was nice to be able to set this up for long…
1 vote -
Choose Default Date For Insert/Update Statements
When auto-expanding an insert or update statement by pressing the tab key, the column list provides default values for the columns. With DateTime and DateTime2 in particular, it would be helpful to configure if you want to use the UTC datetime or the current timezone. Our company exclusively stores datetimes in UTC, so to have this default this way would be extremely helpful!
CREATE TABLE #tmp (ID INT, CreatedDateUtc DATETIME2, Name NVARCHAR(50))
INSERT INTO #tmp (ID, CreatedDateUtc, Name)
VALUES (0, SYSDATETIME(), N''); -- allow this to populate as SYSUTCDATETIME() or GETUTCDATE(), depending on DATETIME2 vs DATETIME1 vote -
NewID() Snippet
I want to create a snippet that will generate a new guid value (the actual value generated from NewId()).
1 vote -
AS keyword
Include a formatting option to "Always include AS keyword for aliases". The goal would be to change
SELECT
*
FROM
[dbo].[Table1] [T]into
SELECT
*
FROM
[dbo].[Table1] AS [T]Note the AS added to the FROM clause. This option could be global (Misc group?) or could be a separate option for each relevant clause (SELECT for field names, FROM and JOIN for table names, etc.).
1 vote -
Dark theme for SSMS
Hi, all. I'm really enjoying using SQL Complete. One feature that's been missing from SSMS is a dark theme. There is a way to hack a "dark theme" -- by changing a setting in a configuration file, but it's incomplete; ‘Object Explorer’ and ‘Output Window’ keep their blindingly white backgrounds. Please consider adding this feature to SQL Complete. Thanks
1 vote -
1 vote
-
Support for ANSI-quoted identifiers
For example
SELECT * FROM "Person" WHERE "Person".0 votes -
Once ON is typed put the name of the current procedure at the top of the suggestion list
When creating a procedure, often the next step is to execute a piece of permission code. ie:
CREATE PROCEDURE db.uspdbForgeSQLComplete
GO
GRANT EXECUTE ON ..... TO .....
GOOnce ON is typed it would be great if the prompts list included the name of the current procedure at the top of the list even if it hasn't yet hit that cache or been created.
0 votes -
Ability to insert frequently used templates without need to modify them
Let's assume, a user have about 10 most frequently used templates that do not need to be modified after they have been inserted unlike snippets.
0 votes -
Option for Line break between tables in join
Multiple tables in the join statement are indented correctly, but no option to add a line break between the table joins. I find this line break to help legibility when dealing with many tables in a join.
I think adding the option "break before JOIN keyword" would solve that issue, and not require evaluating for subquery or further complex on statement conditions.
0 votes -
Wrap string concatenation
Have the option to set max length for concatenation string. I've seen this implemented in SQL Beautifier and it helped legibility on long strings.
User should be able to choose max length of characters before wrapping begins, then wrapping begins with + at beginning of line.
It changes string from long string that user must scroll or have word wrap affect.
BEFORE:
,comment_string = 'Sample text' + 'Sample text' + 'Sample text' + 'Sample text' + 'Sample text'to:
,comment_string = 'Sample text' + 'Sample text'
+ 'Sample text' + 'Sample text'
+ 'Sample text'This would be great to…
0 votes -
Enumerate available event package names and event names in CREATE EVENT SESSION ADD EVENT
Intellisense doesn't enumerate available event package names and event names in CREATE EVENT SESSION ADD EVENT ... clause.
0 votes -
indent logical operator
In a WHERE clause, there is an option to wrap before a logical operator, but then the operator is aligned with the WHERE keyword. I'd like an option to indent logical operators in the WHERE clause, so it's clear that they are under it.
0 votes -
Subquery indentation aligned with paranthesis
Requesting a tweak to the indentation level settings for subqueries.
If I have it set to have closing parenthesis on a new line, I'd like the option to align the whole thing with the starting parenthesis, and this to be the alignment point of the subquery. Increases legibility when lots of subqueries are involved.
Targeted format:
select
1
,2
,3
from
table11 tinner join table2 t2 on t.value = t2.value inner join ( -- starting parenthesis select 1 ,2 ,3 from subquerytable3 where test = test ) f on t.value = v.value and t.value2 = v.value2where
test =…0 votes
- Don't see your idea?