OK, finding a state called Texas in the country of Taiwan, in the state table, blew my mind away!  I actually took the time to look up everything about Taiwan to make sure there was nothing (and I mean nothing) called Texas in Taiwan.  So how did this get in the table?  Some process could have caused the issue with any of the following:

1. The process from one of the source systems did not have data quality checks during entry to make sure this could NOT happen.  The process would need to validate, with their data quality software, the big listing in the sky of all the states in every country.  That obviously did not happen!
2. No process AFTER THE FACT looked at the data and questioned whether this was correct – the data warehouse just accepted the data.  This should have happened in staging prior to load into the data warehouse.

If the data is in the warehouse like that, the following questions need answered:

1. Is there any transactions attached to this record? (Check source and data warehouse, is possible).
2. Find the data steward or SME for the source system and the data warehouse.
3. If there is transactions associated with this record  – we have more to fix!
4. If not, then we can send the information to the "keepers" of the source systems (via the data steward or SME) to make sure it is corrected in the source and does not return to the data warehouse in another process. Or, we can make sure the ETL for the data warehouse does not bring this information again.

After all, who needs a globe when poor data quality can redraw the map with just a few bad pieces of information. There is a Paris, Texas, but there is no Texas in Taiwan.