Schema Difference in Testing Environment and Production Environment

[santhiya]

I am directly connecting with my Testing  database with import mode . I am having the following issues 

I am having few columns that in Testing database that are not in my production database. 
 I am having two tables which has a one to one Relationship due to some bug a key on other end of the table has duplicated value resulting one to Many Relationship but in Production the relationship is one to one 

In development everything works fine, but when I deploy to Production due schema change and relationship mismatch the refresh breaks

Do you have any solution to solve this kind of approach?

[lbendlin]

Remove the extra columns from your "Testing database". You don't want to have these schema differences, especially not when they affect joins.

Consider adding primary keys so that the issue cannot occur at all.