"Edit Top 200 Rows" not working for SQL Server 16.0 - Express Edition

Question

I am trying to "Edit top 200 rows" in SQL Server Express edition, but it's returning with the blank file as shown here:

Showing blank file with disable tools

I have installed this SQL Server on premise. I can select the data and update the data with query, but I'm not able to use the "Edit top 200 rows" feature.

Am I missing some permissions or its not available due to this SQL Server version which include Azure?

I have re-installed SSMS and restarted machine but it doesn't work. I have checked the permissions which are sysadmin. It should work so I can update data directly in the rows.

Answer 1

Installing SSMS 19 resolved the issue for me too.

Available at this link: https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms-19?

A point to note, I could not locate the version 19 immediately using type-ahead. But it can be located clicking the start button and scrolling down.

Answer 2

Did you recently install multiple .NET Framework applications and MS software? If so, you might need to reset your network adapter.

Try running the following command in CMD (Run as Administrator):

netsh winsock reset

Answer 3

SSMS 19.0 resolved my issue. SSMS 18.10 has no support for SQL Server 2022.

Answer 4

SSMS 18 will not work correctly for SQL 2022 databases. Use SSMS 19 for SQL 2022 databases.

While certain aspects work with version 18, some simple operations like right clicking a table and selecting "Edit Top 200 Rows" will return just a blank tab with no errors or notices.

Answer 5

server management studio 19 solves the problem

Answer 6

The same issue happens for me, just all of a sudden for SSMS 19.0 Preview 3.

Installing SSMS 19.1 fixed the issue.
Note: you have to completely uninstall the previous version.

---

Alternatively, if you use Visual Studio (in my case, it's the 2022 version), you can go to View ⇝ Server Explorer ⇝ connect to your database ⇝ right-click on the table you want ⇝ Show Table Data.

This will also allow you to edit it and, by the way, without 200 rows restriction:

Answer 7

I had the same issue. Then I realize that When UPDATE or DELETE queries with BEGIN TRANSACTION, this issue occurred. Because of I forgot to COMMIT TRANSACTION after UPDATE or DELETE queries.

So I apply to COMMIT TRANSACTION, my issue is solved.

Answer 8

SSMS 19 resolves the problem, but I think it important to echo what Pete said. When you install SSMS19 it installs like an update, but actually installs alongside SSMS18 so you need to make sure you are using right shortcuts etc.