Having to select statements by clicking and holding the mouse is just bad ergonomics. Request to have a keyboard shortcut which runs the current sql statement. The current sql statement is defined based on where the cursor is placed. For example, proposed shortcut runs only runs a single sql statement to the next semicolon. This shortcut would be an equivalent to Oracle's SQL developer's ctrl + enter shortcut. Note that this is probably the most used shortcut in SQL Developer and not having an equivalent on SQL Server Management Studio is disappointing. I know that not everyone ends their statements with semicolons but they can carry on manually selecting what they want to run and then pressing F5. But having a shortcut for running the current sql statement would make of a lot of SSMS users extremely happy.

Ssms 2017 doesn't have the capability to use Azure AD authentication in Import/Export wizard.
We have stopped providing Sql authenticated users to support people, we are using AD authentication which works seamlessly. However there is one more place in SSMS which requires the functionality.

When users try to use import export wizard they dont have possibility to use Azure AD authentication instead they need to use a SQL authentication which completely ruins our security setup and going back to the old way of accessing Azure Sql db.

Can the SSMS team add this little functionality so that it does in a secured way and helps in auditing as well. Lot of us were looking for this feature.

There is a bug in SQL Server Management Studio (17.9 and all below) that force the application to crash/restart. In order to reproduce follow the steps below:

1. Select database from the object explorer
2. Press F7 to open Object Explorer Details window and perform a search to object
3. After the search completes, select the object, right click on it and then click "synchronized" from the menu.
4. Then click the `BACK` button several times (fast). You will get the following error:

"There is already a commandd handler for the menu command 'guid goes here: 189."

After several clicks somewhere other the SSMS will crash and restart. Check the screenshots, too.

It appears SSMS v17.7 does not know how to script out the external data source. I am getting this error when attempting to script out an existing data source.

TITLE: Microsoft SQL Server Management Studio
------------------------------

Unexpected value for enumeration type 5. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=14.0.17254.0+((SSMS_Rel_17_4).180502-0908)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.WrongPropertyValueExceptionText&LinkId=20476

Attempting to look at Properties in the right click context menu also produces an error

TITLE: Microsoft SQL Server Management Studio
------------------------------

Cannot show requested dialog.

------------------------------
ADDITIONAL INFORMATION:

Invalid DataSourceType (SqlManagerUI)

Here is the version information:
Microsoft SQL Server Management Studio 14.0.17254.0
Microsoft Analysis Services Client Tools 14.0.1016.251
Microsoft Data Access Components (MDAC) 10.0.16299.15
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.16299.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.16299

When applying filters in Object Explorer (in any "Filter Settings" dialog) in SSMS 17.9.1 and 2018 Preview 6 (and possibly versions prior to 17), it is possible to inject SQL into the query executed by SSMS, simply by using a single quote / apostrophe. Yes, the app code clearly escapes a single apostrophe into two apostrophes, but the string containing the apostrophe is concatenated into a Dynamic SQL string executed via sp_executesql. The string entered via the UI to filter on is intended to be used within a string literal within the Dynamic SQL string. In this case I filtered Stored Procedures, selected "Contains" as the Operator, and passed in "Test" (without the quotes). It generated a Dynamic SQL string containing:

and sp.name like N''%Test%'')'

I then updated the filter Value to be "Te'st" (without the quotes), and it generated the following Dynamic SQL:

and sp.name like N''%Te''st%'')'

which, as soon as it was executed, resulted in an "unclosed quotation mark" error. Full error details are:

-----------------------------------------------------------------
TITLE: Microsoft SQL Server Management Studio
------------------------------

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Unclosed quotation mark after the character string ')
OPTION (FORCE ORDER)
'.
Incorrect syntax near ')
OPTION (FORCE ORDER)
'. (Microsoft SQL Server, Error: 105)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.3045&EvtSrc=MSSQLServer&EvtID=105&LinkId=20476
-----------------------------------------------------------------

That allows me to pass in the following Value for Name such that I could get a case-insensitive comparison in a database that has a binary default collation:

' + CONVERT(NVARCHAR(MAX), 0x5B00540074005D005B00450065005D005B00530073005D005B00540074005D002500) AND 'x' <> '

Once injected and executed, the resulting string evaluates to:

and sp.name like N'%' + CONVERT(NVARCHAR(MAX), 0x5B00540074005D005B00450065005D005B00530073005D005B00540074005D002500) AND 'x' <> '%')

And the CONVERT evaluates to:

[Tt][Ee][Ss][Tt]%

which means that the query becomes:

and sp.name like N'%[Tt][Ee][Ss][Tt]%' AND 'x' <> '%')

The reason for doing the VARBINARY literal is that the "%" and "[" characters are escaped by SSMS and become "[%]" and "[[]", respectively. Hence, this was a way to sneak those characters in ;-).

Full details, including an even easier way of accomplishing the case-insensitive comparison without having to use "[" and "]" around each character, can be found in my answer to the following question on DBA.StackExchange:

SSMS - How to do case-insensitive searches in Object Explorer ( https://dba.stackexchange.com/a/228324/30859 )

In SSMS, when filtering objects in Object Explorer, comparisons on string properties (e.g. Name) use the collation of the database or instance, depending on whether you are filtering database-level or instance-level meta-data, respectively. Hence, when either level is using either a case-sensitive or binary collation, it is not possible to do a case-insensitive search of objects at that level. Having a "case-insensitive" check-box per each filterable Property would be super awesome 😺. Even better might be a "flip case sensitivity" check-box that would then also make it a case-sensitive comparison in an otherwise case-insensitive context.

This situation lead to the following question on DBA.StackExchange, and my answer which was to make use of a SQL Injection bug I found while researching the question:

SSMS - How to do case-insensitive searches in Object Explorer ( https://dba.stackexchange.com/a/228324/30859 )

Ticket for SQL Injection bug: https://feedback.azure.com/forums/908035-sql-server/suggestions/36678803-ssms-object-explorer-filtering-allows-for-sql-inj

When I wish to restore a database from a *.back file, I go into SSMS, select Tasks->Restore Database, and on the dialog, I click the "From Device" radio button, and then click the "..." button to browse to the *.bak file I wish to restore. This then HANGS for MINUTES before the "select a backup device" dialog appears and allows me to drill down and select the backup file.

I have literally HUNDREDS and HUNDREDS (maybe THOUSANDS) of *.bak files on a big data drive with lots of folders. It seems like it might be trying to iterate over all of them and pull information from each file before displaying the dialog. Just a guess, but I can't imagine what else it's trying to do. And it shouldn't need to do that.

It's pretty much unusable. I have to click the "..." and go get like three cups of coffee before it returns and I can continue with my work.