Cannot insert duplicate key row in object

[losintikfos]

Hi Experts;

I am iterating through a Site Object and using the elements values to populate a solution object.

During the iteration process i do encounter duplicates values in the List and hence the exception below when attempt insert:

com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert duplicate key row in object 'dbo.solutionscustinfo' with unique index 'i1'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(Unknown Source)
	at com.billing.essensys.ws.ServiceSync.SolutionCustSyncOne(ServiceSync.java:452)
	at com.billing.essensys.ws.ServiceSync.Run(ServiceSync.java:505)
	at com.billing.essensys.ws.ServiceSync.main(ServiceSync.java:511)

Do anyone know how to control these duplication?

[emceenugget]

This is more of a database question than Java, but you're the "id" column is unique. You will get a database error if you try to insert 2 entries with the same value in a unique column, for example your "id" having multiple entries with value 1. And if that's not what's happening with your program, then I don't know

[ron87]

it is primary key violation problem

[masijade]

it is primary key violation problem

Not necessarily. You can have unique indexes without them being primary keys, and the error itself does not mention "primary key". And the OP already knew it was a unigue index problem.