NCOA data

If you used the preferred vendor you can use the import utility.

Steps ( Search, "NCOA Processing Utility" in the documentation)

1. Place the file on the server and note the path and session number  in the txt.

     a.Check the actions on the NOCA system table to be sure they are correct (tr_nocalink_action)

2. Run the utility

If you did not use the preferred vendor your DB admin will have to do a custom script to import and update. One thing to note is the utility will not archive the addresses only update. So, if you want to keep the old addresses you will need to create some procedure to archive them before running the NCOA. As always run in test first.

Travis

If you used the preferred vendor you can use the import utility.

Steps ( Search, "NCOA Processing Utility" in the documentation)

1. Place the file on the server and note the path and session number  in the txt.

     a.Check the actions on the NOCA system table to be sure they are correct (tr_nocalink_action)

2. Run the utility

If you did not use the preferred vendor your DB admin will have to do a custom script to import and update. One thing to note is the utility will not archive the addresses only update. So, if you want to keep the old addresses you will need to create some procedure to archive them before running the NCOA. As always run in test first.

Travis

We run into this problem of the NCOA process overwriting our data, as well, and I like your idea of archiving the addresses first so we won't have to look in the audit. I wondered if anyone has been able to create such a procedure to before?