Re: Re: Re: Dulpicate data? is it worth de-duping?

I vote for:

De-duping the existing data,
Discovering how dupe data got in there in the first place, and,
Debugging discoveries from #2 so it never happens again.

Depending on your application now, and in the future, duplicate records could become a real nightmare. It sounds like you have reasoned it through and the dupes don't represent a problem, so maybe I'm off base. But after having a problem with 100,000+ dupe transactions getting dumped into a multi-client ecommerce database by renegade code from a know-it-all coder after an unscripted production install... I guess I have issues....

Comment on Re: Re: Re: Dulpicate data? is it worth de-duping?

Replies are listed 'Best First'.
Re: Re: Re: Re: Dulpicate data? is it worth de-duping? by mpeppler (Vicar) on Mar 14, 2002 at 23:46 UTC
Ouch! Removing duplicates from a SQL database is always a fun exercise... I had the dubious pleasure last year, when I discovered that a table on the production system didn't have a unique index on one of the keys, which led to duplicates there, and ultimately, because this was a mapping table for userId values between two systems, to generating duplicate user records. Michael	[reply]
Re: Re: Re: Re: Re: Dulpicate data? is it worth de-duping? by tjh (Curate) on Mar 15, 2002 at 01:22 UTC
Oops. So, hmm. Lol, I started to say 'ok, yours is bigger than mine' because I could easily see that one becoming hell... But I'll refrain :) In any case, these were "opportunities for excellence", eh?. Where's the laugh track when you need it?	[reply]