Post reply

Enterprise Manager Error when trying to delete columns

  • June 2, 2004 at 7:48 am

    #84590

    I get this error when I try to delete or update some columns in a table.

    "Key column information is insufficient or incorrect. Too many rows were affected by update"

    This table has relationship with 2 other tables (Foreign keys in the problem table) Primary in the other tables. Even when I take away the relationship I get this error. What is wrong?

     

    OK I see it is wroking from the Query Analyser. Strange

  • June 7, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • June 7, 2004 at 12:14 pm

    #509305

    Usually I see this when I have a table that has two rows with the exact same data in every column that was defined with no uniqueness in any column. To get around I usually have to add and Identity column to make them unique (even thou they all may be being deleted). Then I can either remove the new column or leave for future need.

  • June 7, 2004 at 3:54 pm

    #509346

    I second what Antares said.  I see the error because there are two or more rows that have the info that you are deleting.  So if you query a table and get the customer firstname, lastname and if you want to delete John Smith, chances are that there are many John Smiths in the table.  Which one does Sql Server need to delete?  You need to pull the primary key as well so that Sql Server knows what row it should delete.

  • April 1, 2005 at 12:15 pm

    #550177

    SQL does not know which file to delete since the data in the rows is exactly the same. Duplicated data usually causes this error...A way to correct this error is to create a new table with the same structure and then copy the content over through Query Analyzer. Then you can delete the old table and rename the new one the exact name of the previous table........

    Or you can clear the contents of the old table and copy everything back from the new table to the old...........

  • April 4, 2005 at 1:46 am

    #550275

    You should do as Antares already suggeted. And once you're done, define a proper PRIMARY KEY on that table, so that you don't run into the same issue again one fine day.

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

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

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