I agree with jscott, the customer creates a lot of these problems. How often do you deliver a quote to add some additional fields and the customer says, "we have these four fields that aren't in use so we'll just re purpose those. But there is some legacy data already there that they don't want cleansed or to pay for some re-names. Aver here in Australia the role of the data analyst is almost non-existant as developers can do that job during build. And with ORM taking over ... I use to specialise in data migration projects but there just aren't the jobs so I have had to change track. Such a shame as we all know you only capture data to use it and if it isn't fit for purpose how can it be used?