SSMS v18.12.1 (also) crashes in edit mode when update a field (varchar(255)) of specific record

Monori, Sandor 21 Reputation points
2022-10-02T16:56:46.007+00:00

Hi All,

In edit mode the ssms crashes when i try to update a field of specific records in table . The column data type is varchar (255). There is no such problem in another table in the database. The error does not occur for other Varchar (255) fields in the table.

I tried to disable triggers on the table, rebuild indexes, create a new copy of table and copy data from the original table, but did not solve it. I tried to backup and restore it on another SQL 2019, but the problem persist there as well.

I tried to turn on SSMS log, but it doesn't log anything, it just turns white (not respondidng).
No entries are made in the sql log, the table works fine otherwise(used by applications). Everything is fine if update the data via TSQL update script.

Any idea how can I diagnose it?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,690 questions
{count} votes

Accepted answer
  1. Erland Sommarskog 100.9K Reputation points MVP
    2022-10-04T20:35:44.887+00:00

    I played with it a little more, and it is obviously a bug in SSMS. I can't see that SSMS submits anything to SQL Server and waits for response. It submits a metadata query which returns successfully.

    I tested this mainly with SSMS 19 Preview 3, in hope that the issue would not appear. And indeed, it did not at my first test, but the contents had been altered due to encoding issues. I also found that the issue may not appear if I perform some other thing first. But if I go straight to the megjegyzes column and enter one character at the end and press Enter, SSMS goes into nirvana.

    You can report bugs related to SQL Server here:
    https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
    Unfortunately, I don't think they accept attachments, but you could link to this thread.

    I would also say that I found it quite cumbersome to update that long column through the grid. A plain UPDATE statement is easier to me.

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Erin Stellato 476 Reputation points Microsoft Employee
    2023-05-25T15:02:26.1933333+00:00
    1 person found this answer helpful.
    0 comments No comments

  2. Erin Stellato 476 Reputation points Microsoft Employee
    2022-10-06T13:24:46.213+00:00

    I've confirmed this also occurs in the latest SSMS 19 preview, and I've logged a bug for it internally. Thanks.

    0 comments No comments

  3. Jacob Wells 0 Reputation points
    2023-01-27T16:19:11.4433333+00:00

    I just had this happen in v18.12.1

    I downloaded the latest version v19.0 hoping it was fixed but it's not.

    Again, no error message, just completely freezes and becomes unresponsive.

    The only other information I can provide is that CPU usage does go up dramatically in task manager, and even the fans on my small pc start ramping up as well.

    0 comments No comments

  4. Erin Stellato 476 Reputation points Microsoft Employee
    2023-01-27T19:50:02.91+00:00

    This fix did not make it into 19.0, we do have it logged as a bug.

    0 comments No comments