5 pts.
 Errors: Violation of UNIQUE KEY constraint ‘UN_FILENAME’. Cannot insert duplicate key in object
when i am migrating data from oracle9i to SQL2005 i am getting the error Errors: Violation of UNIQUE KEY constraint 'UN_FILENAME'. Cannot insert duplicate key in object how should i solve the problem

Software/Hardware used:
ASKED: October 18, 2008  10:41 AM
UPDATED: October 20, 2008  12:57 AM

Answer Wiki:
Sounds like you have created a unique constraint or unique index on the table that didn't exist on the Oracle database, or you are trying to insert the records a second time. It could also be that the Oracle table was case sensitive, while the SQL Server defaults to case insensitive. If this is the case and you have the value "Test" and try to insert the value "TEST" you'll get the duplicate key error. This can be corrected by changing the collation of the column, table or database to a case sensitive collation. If there is no matching constraint on the Oracle database, simply remove the constraint.
Last Wiki Answer Submitted:  October 18, 2008  6:46 pm  by  Denny Cherry   64,520 pts.
All Answer Wiki Contributors:  Denny Cherry   64,520 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Check out my SQL Server blog “SQL Server with Mr Denny” for more SQL Server information.

 64,520 pts.