Thank you for your reply, Stefan.
Stefan Krzywicki (12/26/2012)
Is this being run as a SQL Server job or is it being run from Visual Studio?
The package is being executed in a step of a SQL Server job.
If it is a scheduled SQL Server job, the best way to make sure you're working on the latest package is to open Visual Studio, go to the project in which you'd like to have the package and right click on the SSIS Packages node.
From there, click on Add Existing Package. Select the server where your job is and then select the package. This will create a copy of the current SSIS package. You can alter it to your heart's delight, but no changes will be made to the running job until you save a copy back to the server.
What makes me get confused is there are several projects in Visual Studio (from IntegrationServicesProject1 to IntegrationServicesProject9), all of them having the same subfolder structure, all of them containing the file named "Import Oracle File.dtsx". I would think the file with the latest timestamp would be the one currently deployed, but i'm not sure.
If you need more detail, just let me know.
OK, let's suppose I did the changes to the package. I would have to re-deploy the package back to the server, right?
The package just contains a data transformation from a flat file to a database table, but the new flat file will have more columns than the current flat file. If the new columns are not mapped, they won't be loaded, am I correct?
"A watt of Ottawa" - Gerardo Galvan
To better understand your help request, please follow these best practices.[/url]