Post reply

Conversion/Mirgration Project

  • April 14, 2011 at 8:43 am

    #150143

    Need some advice...

    We are trying to prep some data to load into a new system. Looking at the data below you will see my problem. If then event that the [Name] or [Address-1] or [City] or [Zip] are ANY different from a previous record it was assigned a NEW key (Insurance Number). I know that all of these row *SHOULD* be the same key/entry and not duplicated. How can I resolve this issue before loading the data into the new system?

    ex: insurance 182's are because DALLAS was Spelled DALLAX. Phone number doesn't seem to be effecting it. I think these key generating fields are acting as a natural key. I could be wrong.

    Insurance NumberNameAddress-1CityStateZip Code Number Phone

    165AAGP O BOX 612989DALLASTX75251800-557-8832

    65AAGPO BOX 612989DALLASTX75261800-557-8832

    100AAGP O BOX 612989DALLASTX75261800-557-8832

    182AAGPO BOX 612989DALLAXTX75261800-557-6832

    182AAGPO BOX 612989DALLAXTX75261800-557-6832

    182AAGPO BOX 612989DALLAXTX75261800-557-6832

    182AAGPO BOX 612989DALLAXTX752610

    1478AAGP O BOX 612989DALLASTX75261800-557-8832

  • April 14, 2011 at 9:10 am

    #1311684

    one thing you could grab a free cityname/state/zipcode database off the web(42K rows or so) and join it to your data on city/state/zip and see what doesn't match based on name;

    from there you could update the source, or determine it's ok as far as the source data goes.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Viewing 2 posts - 1 through 1 (of 1 total)

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