database - Data cleansing from un-normal-to normalised tables migration -


i'm cleansing data client. we're migrating legacy helpdesk ms access system customer relationship management package, ms dynamics 2015.

the llgacy system's invoice table un-normal. has in 1 table name of client, ticket number, description of helpdesk query , on.

creates scenario john smith logs helpdesk ticket, 1 instance of john smith, phone number (808-234-123) created each time helpdesk ticket

raised (and 1 row written ticket table). john smith has logged hundreds of tickets , has been entered in database as

name        phone number john smith  (808-234-123) j. smith    (808-234-123) john s.     808234123 johnny smith    ????unknown jonathan smith  234-123 

and on.

what i'd 1. agree business definitive spelling of john smith , actual phone number 2. run sort of cleansing routine\package\whatever update close-to-definitive john smiths definitive john smith

this necessary because dynamics crm uses far more normalised database , want 1 john smith n records, not n john smith n records.

you use analyze tool in access

database tools, , in analyze group, click analyze table

https://support.office.com/en-in/article/normalize-your-data-using-the-table-analyzer-8edbb763-5bab-4fbc-b62d-c17b1a40bbe2


Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -