![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a DTS package with about 20 steps. It's all simple tasks. Nothing elaborate. I'm working with 2 remote shared SQL servers. SQLA and SQLB The DTS package is saved on: SQLB The package empties 4 tables on SQLA (DELETE FROM tasks) Then populates those tables with a bit of data grooming. Last step is to transfer the new data to SQLB. I set the parallel processing limit to 1. If I execute the DTS manually - it works perfect. If I allow the schedule to run the DTS - data is duped in all the tables. Every morning I wake to duped data. I can only guess that the first set of data is not being deleted. How can I troubleshoot this? I don't have any control over scheduling. Are there any settings there that can effect this? thanks! |
#3
| |||
| |||
|
|
How are you deleting the data-- truncate table? Have you tried leaving the old data and only copying over new rows (using SQL instead of a bulk table copy) that makes sure the rows are unique? Randall Arnold "shank" <shank (AT) tampabay (DOT) rr.com> wrote in message news:%23c8gsYebGHA.3632 (AT) TK2MSFTNGP05 (DOT) phx.gbl... I have a DTS package with about 20 steps. It's all simple tasks. Nothing elaborate. I'm working with 2 remote shared SQL servers. SQLA and SQLB The DTS package is saved on: SQLB The package empties 4 tables on SQLA (DELETE FROM tasks) Then populates those tables with a bit of data grooming. Last step is to transfer the new data to SQLB. I set the parallel processing limit to 1. If I execute the DTS manually - it works perfect. If I allow the schedule to run the DTS - data is duped in all the tables. Every morning I wake to duped data. I can only guess that the first set of data is not being deleted. How can I troubleshoot this? I don't have any control over scheduling. Are there any settings there that can effect this? thanks! |
#4
| |||
| |||
|
|
I'm using DELETE FROM. Maybe that's the issue. The data is constantly changing throughout all 4 tables. I just figured it be easiest to dump the old and grab the new instead of comparing record by record. thanks! "Randall Arnold" <randall.nospam.arnold (AT) nokia (DOT) com.> wrote in message news:%23pJgKNgbGHA.4672 (AT) TK2MSFTNGP04 (DOT) phx.gbl... How are you deleting the data-- truncate table? Have you tried leaving the old data and only copying over new rows (using SQL instead of a bulk table copy) that makes sure the rows are unique? Randall Arnold "shank" <shank (AT) tampabay (DOT) rr.com> wrote in message news:%23c8gsYebGHA.3632 (AT) TK2MSFTNGP05 (DOT) phx.gbl... I have a DTS package with about 20 steps. It's all simple tasks. Nothing elaborate. I'm working with 2 remote shared SQL servers. SQLA and SQLB The DTS package is saved on: SQLB The package empties 4 tables on SQLA (DELETE FROM tasks) Then populates those tables with a bit of data grooming. Last step is to transfer the new data to SQLB. I set the parallel processing limit to 1. If I execute the DTS manually - it works perfect. If I allow the schedule to run the DTS - data is duped in all the tables. Every morning I wake to duped data. I can only guess that the first set of data is not being deleted. How can I troubleshoot this? I don't have any control over scheduling. Are there any settings there that can effect this? thanks! |
#5
| |||
| |||
|
|
Try Truncate first. If that doesn't work you may have table structure problems. Randall Arnold "shank" <shank (AT) tampabay (DOT) rr.com> wrote in message news:ec2fG9gbGHA.3712 (AT) TK2MSFTNGP03 (DOT) phx.gbl... I'm using DELETE FROM. Maybe that's the issue. The data is constantly changing throughout all 4 tables. I just figured it be easiest to dump the old and grab the new instead of comparing record by record. thanks! "Randall Arnold" <randall.nospam.arnold (AT) nokia (DOT) com.> wrote in message news:%23pJgKNgbGHA.4672 (AT) TK2MSFTNGP04 (DOT) phx.gbl... How are you deleting the data-- truncate table? Have you tried leaving the old data and only copying over new rows (using SQL instead of a bulk table copy) that makes sure the rows are unique? Randall Arnold "shank" <shank (AT) tampabay (DOT) rr.com> wrote in message news:%23c8gsYebGHA.3632 (AT) TK2MSFTNGP05 (DOT) phx.gbl... I have a DTS package with about 20 steps. It's all simple tasks. Nothing elaborate. I'm working with 2 remote shared SQL servers. SQLA and SQLB The DTS package is saved on: SQLB The package empties 4 tables on SQLA (DELETE FROM tasks) Then populates those tables with a bit of data grooming. Last step is to transfer the new data to SQLB. I set the parallel processing limit to 1. If I execute the DTS manually - it works perfect. If I allow the schedule to run the DTS - data is duped in all the tables. Every morning I wake to duped data. I can only guess that the first set of data is not being deleted. How can I troubleshoot this? I don't have any control over scheduling. Are there any settings there that can effect this? thanks! |
![]() |
| Thread Tools | |
| Display Modes | |
| |