if you have that error (in production), it's not obvious to see which column or row this error comes from, and how to locate it exactly.
it's even more complicated if it's coming from a trigger, for example, and not the original insert/update.

I have seen that oracle meanwhile gives clear information which column the error is raising, which actual data length was passed, and the column's max size.

When we drag something from OE into a query window, then the identifier will always be enclosed in square brackets. Many of us do our due diligence and take care to use identifiers that do not require separators. These separators makes SQL code (a lot) harder to read, and we feel that we are punished with these square brackets. We don't want to do a search and replace all over and over again, when there could just be a setting in SSMS to not generate these.

Msg 8152, Level 16, State 13, Line 2
String or binary data would be truncated.
The statement has been terminated.

A lovely error in a 300 lines of SQL update statement in SQL Server 2005, it does not say what field was truncated, what line was truncated.

Right-click a database, Properties, Files. There's a column named "Initial Size (MB". The word "Initial" should be removed. It is incorrect to have that word there. What we see here is the current size. This is particularly confusing for tempdb since people tend to think that what you see here is indeed the initial size (size at startup, from sys.master_files), which is *not* correct. Again, you see the current size!

This bug led me to think the values were different than actual ones: sometimes, when truncating values due to column width, SSMS 2017 (17.7) doesn't put ellipsis (…) in the end of the truncated value, and users are misled to think the value is not truncated.

SSMS should have a checkbox under Server Properties, on the Database Settings page, labeled something like "Use Backup Checksums" that would toggle the sp_configure setting for "backup checksum default". This would make it easier for people to enable backup checksum default, which is a good "best practice" that the tooling should encourage.

I am running SSMS 17.5 and attaching to an Azure server with 35 Databases and over 50 users.

If I connect to a local DB intellisense works fine. On the Azure server there is nothing. No Intellisense at all. It is turned on (TextEditor -> IntelliSense -> Enable Intellisense) and working against other servers.

My questions are:

Could this be a bug in SSMS 17.5?
Is there a setting in SQL server to disable Intellisense queries?

SQL Server Management Studio 17.6 (version 14.0.17230.0) crashes when I click on the schedule icon for a subplan (from a SQL Server 2016 SP1 CU4 instance). In Event Viewer, I find the following event from ".Net Runtime":

Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog.InitializeControls()
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog..ctor(Microsoft.SqlServer.Management.SqlMgmt.JobScheduleData)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.ChangeShedule()
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.grid_MouseButtonClicked(System.Object, Microsoft.SqlServer.Management.UI.Grid.MouseButtonClickedEventArgs)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseButtonClicked(Int64, Int32, System.Drawing.Rectangle, System.Windows.Forms.MouseButtons)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.HandleButtonLBtnUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.ProcessLeftButtonUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)

Copy Database Wizard is not working for local copy operation. v17.5 There are previous bug reports when trying to copy a SQL201x -> SQL2017 DB using management studio 17.x . However, it appears you cannot copy a SQL2017-SQL2017 DB as well using the same wizard using the SMO option when copying without taking the DB offline. ERR: Property HasMemoryOptimizedObjects is not available for Database '[test]'
File attached

- Searching removes the "top ideas" option
- no subproduct or labelling (SSIS, SSRS, etc)
- Search is useless "ssis text qualifier embedded" I want all keywords not results like "VS 2017 SSDT SSIS Dark Theme fail" which contains

Unless it's by design?

When you enable the parameter "SET SHOWPLAN_TEXT ON; " The first query execution goes well and produces a query plan in text format, but the second one causes an error at the level of "mscorlib "

In SQL Server Management Studio 2008 RC0, when you enter "newsequentialid()" as the "Default Value or Binding", SSMS gives a dialog box that says "Error validating the default for column XYZ. Do you want to cancel your changes?"

This error message occurs whether or not you have set the RowGUIDCol property on the xolumn.

I have seen similar feedback items, mostly for SQL 2005, but there seems to have been no resolution in several years. I hope this can get fixed for SQL 2008.

While creating a maintenance plan, click on the scheduler icon to create a schedule, the application crashes.

When adding a database that has case sensitive collation to Availability Databases (SSMS -> Always On High Availability -> Availability Groups -> Group Name) it will fail with the following error: "The multi-part identifier "a.delimited" could not be bound".

In Management Studio V17.4 me and my colleague both gets the error "Input string was not in a correct format. (mscorlib)" when we have first executed the SET SHOWPLAN_ALL ON statement and do a simple select like SELECT * FROM sys.objects afterwards

This works in SQL 2016, so something must be broken in SQL 2017

When trying to enable page compression on an index through the GUI (SSMS 17.4), I get the following error: "Object reference not set to an instance of an object".