Using SSMS to "Edit top 200 rows" on a 2000 server and getting a weird error.

Question

Post reply

Using SSMS to "Edit top 200 rows" on a 2000 server and getting a weird error.

Kenneth.Fisher

SSC-Insane

Points: 20396
More actions
April 20, 2012 at 3:25 pm

#100472

I would supply sample tables and data but to be honest I can't replicate the problem. When I right click on the table and say "Edit top 200 rows" then try to edit one of the rows I get the following error:
No row was updated.
The data in row 1 was not committed.
Error Source: Microsoft.SqlServer.Management.DataTools.
Error Message: The row value(s) updated or deleted either do not make the row unique or they alter multiple rows(2 rows).
Now I have created a duplicate table, same structure, same indexes, same data and everything works correctly. I've dropped and recreated the indexes with no luck. I've checked for duplicate entries and run a CHECKDB.
Anyone have any suggestions?
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

Does this happen to all tables or only certain tables?

Kenneth.Fisher SSC-Insane Points: 20396 More actions · Answer 2

Just the one table. I even created an exact duplicate, indexes, triggers, data everything and didn't get the same error.

Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

Jayanth_Kurup SSC-Insane Points: 22967 More actions · Answer 3

I am guessing here , but have you looked closer at what the trigger is doing ?

Jayanth Kurup[/url]

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 4

Is there a unique or primary key on the table? I've seen that type of error from applications where the datasets couldn't identify a unique key of some sort.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Kenneth.Fisher SSC-Insane Points: 20396 More actions · Answer 5

I've dropped both the trigger and the only unique index. Still no luck.

Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

Jayanth_Kurup SSC-Insane Points: 22967 More actions · Answer 6

the only other thing i can think of would be collations.

Jayanth Kurup[/url]