July 23, 2010 at 8:28 am
I have a transactional database that contains many duplicate "Customers" and I want to merge the duplicates. Would it be sufficient and acceptable to substitute Customer A's unique identifier everywhere in the database where I find Customer B's (this is duplicate) unique identifier? Are there any other dependencies that I need to account for? I know many applications have a Merge functionality, but I'm wondering exactly what takes place behind the scenes to execute this.
Thanks
July 30, 2010 at 3:04 am
[font="Verdana"]Instead of merging the duplicates, you need to remove it. You need to do this work around for the other dependent objects as well which are dependent on Customer's table. Just check out on google what are the techniques for removing duplicates.
By the way, what version SQL Server you are working on? If its SQL Server 2000, there is a bit tedious work around as compare to SQL Server 2005.
Let us know on this.
Thanks,
Mahesh
[/font]
MH-09-AM-8694
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply