<turbo-stream action="update" target="wiki_card"><template>

<h1>E2059 Cannot insert duplicate key row in object</h1>
<div class="trix-content"><p>The error message is related to a <strong>duplicate key violation</strong> in a Microsoft SQL Server database.<br><br><strong>E2059 - ECE_ForwardedSQLError: Native Error Code: 2601 SQL State: 23000 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert duplicate key row in object 'dbo.Demo$Pricebook' with unique index '$9'. The duplicate key value is (1, 1, 0, 1, 1, 1, 1, A0000001, 1.18000, 0.00000000000000000000, , , Dec 23 2024 11:00AM, SKU, A0000001, 10009).</strong></p><p><strong>Error Breakdown:</strong></p><ul><li><strong>E2059 - ECE_ForwardedSQLError</strong>: This is a system-specific error code related to forwarded SQL errors.</li><li><strong>Native Error Code: 2601</strong>: This is an SQL Server error code indicating a <strong>duplicate key insertion violation</strong>.</li><li><strong>SQL State: 23000</strong>: This SQL state corresponds to an <strong>integrity constraint violation</strong>.</li></ul><p><strong>Error Message</strong>:&nbsp;</p><ul><li><code>Cannot insert duplicate key row in object 'dbo.Demo$Pricebook' with unique index '$9'</code></li><li>SQL Server is preventing an <strong>INSERT</strong> operation because it would create a <strong>duplicate entry</strong> in a table with a <strong>unique constraint</strong> (index <code>$9</code>).</li><li><strong>Duplicate Key Value</strong>: <strong><code>(1, 1, 0, 1, 1, 1, 1, A0000001, 1.18000, 0.00000000000000000000, , , Dec 23 2024 11:00AM, SKU, A0000001, 10009)</code></strong><ul><li>This represents the values that are causing the duplication.</li></ul></li></ul><p>The table <strong><code>dbo.Demo$Pricebook</code></strong> has a <strong>unique constraint</strong> (likely a <strong>primary key</strong> or a <strong>unique index</strong>).The insert operation is trying to add a row with the same key values that already exist.The <strong>unique index </strong><strong><code>$9</code></strong> enforces uniqueness on a specific combination of columns, and your new row has the same values as an existing row in that index.<br><br><strong>Possible solutions:</strong></p><ul><li>Check if the Data Already Exists - run a SQL query to find out if the record exists. If this query returns a result, the record <strong>already exists</strong>, and you need to avoid inserting it again.</li><li>Check the Unique Constraint : Find out which columns are included in the unique index <code>$9</code>.</li><li>In any case, you can filter this record out on the Rapidi transfer so you can allow other records to be created and/or updated while you review this particular record.&nbsp;</li></ul></div>
</template></turbo-stream>

