jevogelsong (2/13/2014)
It was a existing package I am trying to edit so I would assume so. Please mind any ignorance on my part I only have a minor in SQL, filling in for our real DBA. II first ran a import data wizard on the destination DB to bring over the new tables and that went fine. The scheduled job has 2 steps, the first is T-SQL to truncate the destination tables, which works fine (as the tables are now blank). The 2nd step is the SSIS package, which I was able to open and edit and add the new tables, but they are not populated. I did edit the job under my account and then re-opened it via the SQL agent account and it still looks fine, but I am still missing something.
Its a small package I am wondering if it is worth building a new one?
It is unlikely that the package you have edited is the same as that which is deployed.
Click on the package in your solution and check its 'Full Path' property.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.