Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6931695
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T11:36:40+00:00 2026-05-27T11:36:40+00:00

I just found out that a table on my production server (which holds approx.

  • 0

I just found out that a table on my production server (which holds approx. 35K records) contains 588 duplicate entries in an INT(11) column which has AUTO_INCREMENT.
The UNIQUE key is missing on that column so that’s probably the cause.

Any ideas on how to give all duplicate entries a unique ID and then adding the UNIQUE key to the column so this will never happen again?

Table schema:

CREATE TABLE `items` (
 `item_ID` int(11) unsigned NOT NULL auto_increment,
 `u_ID` int(10) NOT NULL default '0',
 `user_ID` int(11) NOT NULL default '0',
 `p_ID` tinyint(4) NOT NULL default '0',
 `url` varchar(255) NOT NULL,
 `used` int(10) unsigned NOT NULL,
 `sort` tinyint(4) NOT NULL,
 `last_checked` int(11) NOT NULL,
 `unixtime` int(11) NOT NULL,
 `switched` int(11) NOT NULL,
 `active` tinyint(1) NOT NULL default '0',
 UNIQUE KEY `unique` (`p_ID`,`url`),
 KEY `index` (`u_ID`,`item_ID`,`sort`,`active`),
 KEY `index2` (`u_ID`,`switched`,`active`),
 KEY `item_ID` (`item_ID`),
 KEY `p_ID` (`p_ID`),
 KEY `u_ID` (`u_ID`)
) ENGINE=MyISAM AUTO_INCREMENT=42755 DEFAULT CHARSET=utf8
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T11:36:40+00:00Added an answer on May 27, 2026 at 11:36 am

    How about something like this? Again test it on a backup first.

    # Copy duplicate records
    CREATE TABLE newitem SELECT * FROM items WHERE item_ID IN 
        (SELECT item_ID FROM itemd GROUP BY item_ID HAVING COUNT(*) > 1);
    
    # remove auto increment from id in new table
    ALTER TABLE newitem DROP INDEX Item_ID, MODIFY item_ID int;
    
    # delete duplicates from original
    DELETE FROM item WHERE item_ID IN (SELECT DISTINCT item_ID FROM newitem);
    
    #Update column to be primary key
    ALTER TABLE items DROP INDEX Item_ID, ADD PRIMARY KEY (Item_ID);
    
    # Set new duplicate ID's to null
    UPDATE newitem SET item_ID=NULL;
    
    # Insert records back into old table
    INSERT INTO item SELECT * FROM newitem;
    
    # Get rid of work table
    DROP newitem;
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

To my surprise I just found out that applying text-alignment to a table column
I just found out that in order to prevent full table scans during joins,
Just found out that the video output of the iPad is not a system
I just found out that by converting PNG32 to PNG8 via Photoshop will fix
I just found out that my program is losing 5% execution speed when it
I just found out that in FF, if you are dynamically creating an OPTION
I just found out that lazy loading in Entity Framework only works from the
I’ve just found out that the execution plan performance between the following two select
I've just found out that there is a possibility to host a Windows Forms
I have an interview tomorrow morning and just found out that I will also

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.