3 ms·
People at my old company would do a lot of "data archaeology". They would find a table in a T-SQL database named "facilities", and a table in an SAP system call
by brundolf 6y ago
People at my old company would do a lot of "data archaeology". They would find a table in a T-SQL database named "facilities", and a table in an SAP system called "units", and then would notice that the numeric "facility_id" column's values had a lot of overlap with the string IDs in "unit_id", if you remove the underscore prefix at the front, and then they'd email the client's data people to confirm that these were in fact the same entities, and then they'd associate them in their cross-database-querying tech, and ta-da. A huge amount of new data cross-pollination is available.
- quacked 6y agoI'm starting to wonder if I should quit my job, buff up on SQL, and go into data consulting. Everyone on HackerNews talks a big game about FAANG and their copycats trying to leverage machine learning techniques to increase profit margins, but the bulk of legacy businesses seem to not even have the facility to make sure that client_ID is stored properly across their massive realms of siloed databases.