![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We are using a dynamically created DTS package to do a complete push replication from our production system to our public-facing website. Recently, our DTS package has started to throw errors like to the following (Culled from the DTS DataPump log, obviously) ---- Execution Started: 6/9/2005 8:12:15 AM Error at Destination for Row number 25068. Errors encountered so far in this task: 1. Error Source: Microsoft OLE DB Provider for SQL Server Error Description:The statement has been terminated. Error Help File: Error Help Context ID:0 Error Source: Microsoft OLE DB Provider for SQL Server Error Description:Violation of PRIMARY KEY constraint 'PK_Policy'. Cannot insert duplicate key in object 'Policy'. Error Help File: Error Help Context ID:0 ---- The destination table is truncated in the prior step, before the datapump task executes. The source table is clean (no duplicate PKs). The primary key column is proc-generated rather than Identity(1,1) not null. The DataPump task properties have not been changed, same database names, same schemas, etc. The DataPump task is set to use fast load, with a max error count of 0. |
#3
| |||
| |||
|
|
We are using a dynamically created DTS package to do a complete push replication from our production system to our public-facing website. Recently, our DTS package has started to throw errors like to the following (Culled from the DTS DataPump log, obviously) ---- Execution Started: 6/9/2005 8:12:15 AM Error at Destination for Row number 25068. Errors encountered so far in this task: 1. Error Source: Microsoft OLE DB Provider for SQL Server Error Description:The statement has been terminated. Error Help File: Error Help Context ID:0 Error Source: Microsoft OLE DB Provider for SQL Server Error Description:Violation of PRIMARY KEY constraint 'PK_Policy'. Cannot insert duplicate key in object 'Policy'. Error Help File: Error Help Context ID:0 ---- The destination table is truncated in the prior step, before the datapump task executes. The source table is clean (no duplicate PKs). The primary key column is proc-generated rather than Identity(1,1) not null. The DataPump task properties have not been changed, same database names, same schemas, etc. The DataPump task is set to use fast load, with a max error count of 0. |
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
|
I'm not sure what you're asking, Hilary... I'm not seeing a reference to an error 1805 in my earlier message? |
#7
| |||
| |||
|
|
I'm not sure what you're asking, Hilary... I'm not seeing a reference to an error 1805 in my earlier message? |
#8
| |||
| |||
|
|
I'm not sure what you're asking, Hilary... I'm not seeing a reference to an error 1805 in my earlier message? |
#9
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |