Add the ability to force the AS keyword in SELECT statements:

SELECT TT.Column1 Alpha FROM dbo.TestTable AS TT
becomes
SELECT TT.Column1 AS Alpha FROM dbo.TestTable AS TT

----

Add the ability to format SELECT clause aliasing using the Alias = Value syntax:

SELECT TT.Column1 AS Alpha FROM dbo.TestTable AS TT
becomes
SELECT Alpha = TT.Column1 FROM dbo.TestTable AS TT

This would make refactoring INSERTS/UPDATES much more convenient.

Add the ability to insure the 'AS' keyword is always used when aliasing tables in FROM/JOIN statements:

SELECT * FROM dbo.TestTable TT
becomes
SELECT * FROM dbo.TestTable AS TT

Allow alignment of AS clauses across joins, even if 'Place on new line' options are not enabled.

When doing an INSERT INTO it would be nice if you could type INSERT INTO TableName (*) then if you tabbed after the * it would expand out all the columns for that table.

Be able to highlight a chunk of SQL and right click and create a new Stored Procedure or function out of it and then it would replace the highlighted SQL with a exec statement to exec that new sp that was just created.

Please add option to "Automatic tab renaming" which should automatically update tab name, based on written query.

When writing select queries, I don't always want to qualify all column names with a table or alias name, but when I do a join I want to always have the table name or alias that the column comes from. E.g.:

If you have 2 tables, Table1 and Table2 and each table has 1 Column Table1.Col1 and Table2.Col2

SELECT Col1
FROM Table1
JOIN Table2
ON Col1 = Col2

That query will work just fine, but what I'd like to see when I format it is:

SELECT Col1
FROM Table1
JOIN Table2
ON Table1.Col1 = Table2.Col2

For auto-generated Insert scripts, provide an option to exclude columns with a Default Value set, possibly drilled-down by data type.

E.g. if a, say, DateTimeCreated column has a default value of GETDATE(), or CreatedByUser one has a default value of suser_name(), include or omit such columns when generating the insert scripts based on the stated preferences.

For an EXEC I would like to be able to choose not to place parameters on a new line if shorter than the wrap column. I cannot see how to do this for an EXEC statement.

I have logging functions that I do not want exploded into multiple lines because they take far too much space

e.g.

EXEC audit.usp_Log 'Validation', @ValidationProcedureName, @Title = '@ValidationProcedureName', @Value = @DataSetID;

Add a Describe as Table context menu option to any selected query or result sets

This would take the query, push it through sys.sp_describe_first_result_set, and create a Table variable for it

This would make capturing interim results in complex queries much less tedious

When SSMS start and had tabs opened, it tries to reconnect to each tab and the startup is extremely slow especially if a server is not available (it happens very often when working with VPN's customers, for instance).
What about a servers list to which to reconnect, instead of an on/off feature? We could enable for local and disable for external servers, for instance

Import "Tab History" feature of SQL Prompt in Visual Studio, just like it is in SSMS. That feature is beautiful just the way it is in SSMS, would be nice to have it in Visual Studio as well.

In order to share format styles across our team, we have a shared folder that holds our standard styles. Only problem is, after a reboot that folder doesn't always reconnect automatically. SQLPrompt then defaults to the local C:\ folder, which might have the outdated version of the styles. I'd rather it throw an error or alert me in some way that my default styles are not available.

HI Redgate Team,

it would be amazing to get the option to view an extended event target within SSMS in a grid.

Something like this.

http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/12/12/an-xevent-a-day-12-of-31-using-the-extended-events-ssms-addin.aspx

Thanks for looking into this!

Torsten
Friend of Redgate

It would be useful to display the original columns Description (Extended Property) when you hover over the Results column header, just like you do it with the Columns of a Table

I created a query that joins tables from another database (dbname..tablename) and had to join another table from that database.
The table I wanted to use came up as a suggestion because of the relation between those two tables. So I selected the table, but the databasename prefix wasn't added. That was a bit unfortunate

Just as it is possible to align comparison operators for =, <>, <, >, etc. would it then be possible to add BETWEEN, LIKE, NOT LIKE as well?

Give us the ability to disable the column picker for an IN clause, so that when you're trying to say "IN (3,4,5)", it doesn't keep popping up suggestions for a field.