Last updated: October 13, 2026
When you right-click a table in SQL Server Management Studio (SSMS), you may see the Edit Top 200 Rows option. By default, this opens an editable grid containing up to 200 rows.
But what if you need to edit 500, 1,000, or more rows?
You do not need to modify your table or use a different database tool. SSMS provides two ways to work beyond the default 200-row limit:
These methods are useful for SQL Server Management Studio 2008 and versions of SSMS that provide the same editing options.
If you frequently need to edit more than 200 rows, changing the default setting is the simplest option.
Follow these steps:
SSMS will now use the new row limit when opening the table’s editable grid.
Example: If you change the value from 200 to 1000, SSMS can display up to 1,000 rows for editing instead of 200.
Can you set the value to 0?
Yes. Setting the value to 0 removes the row limit, allowing SSMS to retrieve all rows.
However, this is not recommended for large tables. Loading an entire table into the editing grid may affect performance or make it harder to work with the intended records.
For most situations, choose a reasonable limit instead of loading every row.
If you only need to change the limit for a particular table or editing session, you can modify the query without changing your default SSMS settings.
Follow these steps:
For example, the generated query may look similar to this:
SELECT TOP (200)
[CustomerID],
[CustomerName],
[Email]
FROM [dbo].[Customers];To retrieve up to 500 rows, change it to:
SELECT TOP (500)
[CustomerID],
[CustomerName],
[Email]
FROM [dbo].[Customers];The editable results should now display up to 500 rows, depending on how many records exist in the table.
Important: This method changes the number of rows retrieved for that editing session. It does not permanently change your SSMS default setting.
You can also refine the query to retrieve specific records. For example, if you need to work with a particular range of customers, use an appropriate WHERE condition rather than retrieving unrelated rows.
These two SSMS options serve different purposes.
| Option | Purpose |
| Edit Top 200 Rows | Opens an editable grid for working with table records. |
| Select Top 1000 Rows | Opens a query that retrieves records for viewing and analysis. |
Changing the limit for Select Top Rows does not automatically change the Edit Top Rows limit.
If your goal is to edit records through the SSMS grid, make sure you change the Edit Top Rows setting.
When you want to change certain records, an SQL UPDATE statement is probably the better option than just editing a huge grid.
For example, suppose you want to update the email address of one customer.
First, verify the intended record:
SELECT CustomerID, CustomerName, Email
FROM dbo.Customers
WHERE CustomerID = 105;Then run the update:
UPDATE dbo.Customers
SET Email = 'newemail@example.com'
WHERE CustomerID = 105;Always include the correct WHERE condition when you’re updating specific records. If you omit the WHERE clause entirely, the UPDATE statement could end up updating every row in the table.
Before making changes to important databases, verify the affected records, confirm your permissions, and follow your organization’s backup and change-management procedures.
If the steps above do not work as expected, check the following.
Reopen Tools > Options > SQL Server Object Explorer > Commands and confirm that you changed Value for Edit Top Rows command, not Value for Select Top Rows command.
Close the existing editing grid and open it again so the updated setting is applied.
Check whether your database account has permission to update the relevant table.
Also check that the result set is editable. If your query joins multiple tables, uses aggregation or returns rows that SSMS can’t uniquely identify, then it may not be editable in the grid.
Increasing the default limit is not always the best solution.
Retrieving too many records can slow down the SSMS editing grid. If you only need to modify specific records, use filters or a carefully written UPDATE statement.
You may encounter the following error when changing a table’s design:
Saving changes is not permitted. The changes that you have made require the following tables to be dropped and re-created.
This issue is different from the 200-row editing limit.
The warning usually appears when you change a table’s structure, such as a column’s data type, nullability, or position, and SSMS determines that saving the change would require re-creating the table.
You can find the related setting under:
Tools > Options > Designers > Table and Database Designers
Look for Prevent saving changes that require table re-creation.
Although this option can be turned off, doing so is generally not recommended. Re-creating a table can introduce risks, including the loss of certain metadata or data.
For structural changes, use a reviewed database migration or the appropriate ALTER TABLE statement rather than disabling the safeguard to get around the warning.
Go to Tools > Options > SQL Server Object Explorer > Commands. Under Table and View Options, change Value for the Edit Top Rows command from 200 to 1000, and click OK.
You can set the Edit Top Rows value to 0 to remove the default limit. However, loading all records is not recommended for large tables. Use a reasonable limit or target specific rows instead.
No. Changing the setting only affects how many rows SSMS retrieves for editing. Your database records are modified only when you actually make and save changes.
Yes. Open Edit Top 200 Rows, display the SQL Pane, and modify the generated SELECT TOP (200) statement to retrieve the required number of rows.
Yes. The original SSMS 2008 workflow uses the same general approach: changing the row limit through SSMS options or modifying the query in the editing window. Menu labels and layout may vary between versions.
The 200-row limit in SQL Server Management Studio is a default setting, not a restriction on the number of records your database can store or update.
If you regularly work with larger sets of records, change the default Edit Top Rows limit. For occasional edits, modify the query for the current session.
For larger or sensitive database updates, a targeted SQL statement is often a better choice than editing hundreds of records manually.
Working with an aging SQL Server application?
InApp helps organizations modernize legacy applications, improve database integrations, and update software systems while maintaining business continuity.
