![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Do you have primary keys in this table ? If you can set one, then you shouldn't have repeated rows and you could find when they duplicate... Josep. "Jonathan Hwang" <JonathanHwang (AT) discussions (DOT) microsoft.com> escribió en el mensaje news:CCC02282-FF89-44C4-9B28-2E2CF5D6A999 (AT) microsoft (DOT) com... I have designed and scheduled running of a very simple sql 2000 DTS package. Out of my years of experience, I have not encounter this problem before. However if you know, you must be an expert! Well... I am trying to schedule a job to run during off peak hours to copy 13 million records from a production table to my standby server. Same table to same table..no special tricks... column to column... I have set a transaction read committed property and 5000 as my batch size as my package property. For nights now...and it completed, however, it duplicated all my rows... so I have 26 million on my destination table! in production, there were only 13 million... The job actually completed successfully and the history only has one entry for the run! Any setting in SQL job or within package that I'm not aware of? Help!! |
![]() |
| Thread Tools | |
| Display Modes | |
| |