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. I
I 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.
Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this
If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.