306 results found
-
Put variables in VALUES clause when expanding INSERT statement
You type in an insert statement. " Insert into dbo.Party" and then press tab. The below code is generated
INSERT INTO Party
(
PartyTypeId,
TenantId
)
VALUES
(
0 /* PartyTypeId - INT NOT NULL /,
0 / TenantId - BIGINT */
)Because most of the inserts, updates etc are mostly used inside stored procedures, and the values come from variables, I would like it to show :
INSERT INTO Party
(
PartyTypeId,
TenantId
)
VALUES
(
@PartyId /* INT NOT NULL /,
@TenantId / BIGINT */
)An updated statement will do the following snippet :
UPDATE Party…
4 votes -
alias second table reference
Automatically alias a second reference to a table even if "generate alias on commit" is not enabled
4 votes -
Ident guide lines
Visualize the ident guide lines in the document.
4 votes -
Ability to define default values for stored procedure parameters expanded by pressing Tab
When you type out "execute SPROCname" and then press Tab, SQL Complete very nicely builds out the list of parameters with commented out datatypes. Really like that. The one thing that would take this from being good to great would be if it filled in any default values from the procedure. Now that would be fantastic!
4 votes -
4 votes
-
Improve standard filtering in Object Explorer
The standard filtering in Management Studio Object Explorer is rudimentary at best. I lack the ability to select multiple values, and use drop downs to do so. Or even better, use complex queries (with and/or/not), and maybe even save and reuse these for daily administration (much like snippets).
4 votes -
Enhancing Execute-Current-Statement with Execute-Current-Selection
I love SQL Complete's execute-current-statement functionality. I think it would greatly enhanced if it would automatically execute highlighted code. This could be a simple check: normally just execute-current-statement if no code is highlighted, but do a default SSMS execute (normally F5) if code has been highlighted.
I know I could always hit F5 but I think having both under the same keyboard shortcut would be very helpful. I never realized how useful it was until I began switching back to SSMS from Toad.
4 votes -
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…
4 votes -
Create a variable table based on a available table in the schema
DECLARE @table varchar(100)
SET @table = 'claims'DECLARE @noScale varchar(255)
SET @noScale = 'INT,TINYINT,BIGINT,MONEY,SMALLMONEY'
SET @noScale=@noScale+',BIT,SMALLDATETIME,DATETIME' --Need for SQL2000
SELECT colName = ',' +
CASE
WHEN C.CHARACTERMAXIMUMLENGTH IS NOT NULL
THEN C.COLUMNNAME + ' ' + UPPER(C.DATATYPE) + '(' + CAST(C.CHARACTERMAXIMUMLENGTH AS varchar(10)) + ')'
WHEN C.NUMERICSCALE IS NULL
THEN C.COLUMNNAME + ' ' + UPPER(C.DATATYPE)
WHEN C.CHARACTERMAXIMUMLENGTH IS NULL AND CHARINDEX(C.DATATYPE, @noScale) > 0
THEN C.COLUMNNAME + ' ' + UPPER(C.DATATYPE)
WHEN C.NUMERICPRECISION > 0 AND CHARINDEX(C.DATATYPE, @noScale) = 0
THEN C.COLUMNNAME…4 votes -
Snippets - Add Predefined Literals for Date Parts
I would like to be able to use a different format for the DATE predefined literals than YYYY-MM-DD. It would be helpful to include one for YYYYMMDD ... or have literals for YEAR, MONTH, and DAY so I could create my own combination from them.
4 votes -
Shortcut for partial selection
I'll be very glad if I could select a partial script in smart way and then run it with CTRL + SHIFT + E shortcut. The separator should be 2 blank lines, one at the top and one at the bottom of the script, and yes, I'm a shortcut addict. thanks a lot guys!
4 votes -
Saved Filters in SSMS
Within SSMS, allow for the saving of filters.
Justification:
Particularly within large databases, often there is a reoccurring need to work with just a subset of tables. Sometimes, within different contexts, the particular subset changes. Being able to easily apply commonly used filters can allow increased productivity by eliminating frictional work (e.g. scrolling and hunting). Additionally, when filters across object types can be applied, there can be a lot of power. For example, being able to filter a particular set of SQL Agent Jobs, associated tables, and procedures related to those jobs, allows a troubleshooting developer to quickly set into…4 votes -
SQL Operations Studio Support
Microsoft Introduced a new Query tool: SQL Operations Studio
I wonder if you would be able to build a support for that tool?
4 votes -
Add setting for color of "highlight Occurrences" or document where this is control in SMMS.
There is a choice on Options > General named Highlight Occurrences. I don't like the way this looks with my color scheme. Suggestion: allow me to change the default highlight color or document where that color comes from in SMMS's color settings.
4 votes -
New Query Template
It can possibly be done with the 'snippet', but when I hit Ctrl- N in SSMS, it would be great if 'my' standard template opened. This allows me have the necessary 'set' options pre configured etc
4 votes -
Add option to adjust function tooltip font size
The tooltip font is just too small ...
4 votes -
Refactoring feature: Add Quotes to names
it would be very helpful if you have an option that encloses object names in quotes. The option should allow you to specify the quote characters to use (brackets vs quotes).
This would transform references like:
dbo.myTable
To
[dbo].[myTable]It would also be nice if this option could be set to be applied during auto-complete.
4 votes -
Separate (one-line) format for simple "when then else end" statement
It would be nice to be able to specify a separate format for simple case statements with only one 'when' and possibly an 'else' clause. These can typically easily fit in one line, while complicated case statements benefit from taking up the additional lines to improve readability.
declare @profit float = 10
/* Simple case statement can fit on one line */
select case when @Profit > 0 then 'Great' else 'Not so great' end/* Complex case statement requires multiples lines */
select case
when @Profit > 10000 then 'Nice!'
when @Profit > 0 then 'OK'
else 'You''re fired!'…4 votes -
Don't qualify column name in certain scenarios
Currently SQL Complete has an option to automatically qualify column names. Unfortunately, turning the option on means turning it on for everything.
I love that SQL Complete qualifies the column name with the table name in regular SELECT statements such as:
SELECT t1.Column1, t2.Column2 FROM dbo.Table1 t1 JOIN dbo.Table2 t2 ON t1.Column1 = t2.Column1
However, I find it unnecessary when you are dealing with only one table in an UPDATE/INSERT/DELETE statement. For example qualification is unnecessary in the following statements:
UPDATE dbo.Table1 SET Column2 = 123 WHERE Column1 = 10
or
INSERT INTO dbo.Table1 (Column1, Column2) ...
or
DELETE FROM…4 votes -
Autocomplete picklist wider
If would be great if the autocomplete pick list was resized sqlcomplete would remember this size change.
4 votes
- Don't see your idea?