Ok so I'm cleaning up some data to go into a CRM , the usual suspects can't do it because there is too much of it so it needs some sick SQL. Of course the ETL team denormalise the data and expect to join using Alpha values such as surname .
Do you:
A. Take the data and format it , call it job done? The data however has links to other data that will be manually changed, when you load it then you will see the load logs approach GBs.
B. Take the data and link it to the referenced manually modified data so changes are reflected in the denormalised data you load for the activities. Yes when I load an activity the link data is the Contacts name . Then get told by the one who asked you to do it (who doesn't understand why records need an identifiable key) & Your Boss who is non technical that you are over complicating things and you think WTF???
C. Get a real job.
Any ideas, personally I'm just going to let it ride, far too comfy here. But it was annoying.
Do you:
A. Take the data and format it , call it job done? The data however has links to other data that will be manually changed, when you load it then you will see the load logs approach GBs.
B. Take the data and link it to the referenced manually modified data so changes are reflected in the denormalised data you load for the activities. Yes when I load an activity the link data is the Contacts name . Then get told by the one who asked you to do it (who doesn't understand why records need an identifiable key) & Your Boss who is non technical that you are over complicating things and you think WTF???
C. Get a real job.
Any ideas, personally I'm just going to let it ride, far too comfy here. But it was annoying.
Comment