Hello,
I built an SSIS package to load data from some flat files into an SQL Server 2005 database. The data is loaded into a set of tables on a staging database. After that it is manipulated and loaded into the data warehouse and the Analysis Services cube is processed. I developed this package on a test Server. It uses an XML Configuration file to configure the paths to the various flat files. The configuration file also contains the destination server names (SQL Server, SSIS Server and SSAS server) and database names.
By default, the package looks to the local D: Drive for the flat files. After testing, this was deployed to Production. I modified the configuration file to point to a network share for the source flat files and to the production servers. I manually ran the SSIS package via SSMS and it ran successfully. Here's where things get weird. I created an SQL Agent Job to run this every night. It runs successfully (no errors and pulling data from the flat files on the network) except that it's still loading data into the test server!
My first thought is that maybe the SQL Server Agent's service account (which is a domain account and not the default NetworkService account) might not have access to theC:\Program Files\Microsoft SQL Server\90\DTS\Packages\ folder in order to read the XML Configuration file, and therefor, it is falling back to the values that I used when I developed the package. (i.e. pointing at the test server.) But if that were the case, I would expect that i would also try to find the source files on the D: Drive instead of the network share that I indicated within the config file.
So I'm at a loss. How could this package run fine on the Production server when I run it directly, but switch back to the test server when the SQL Agent launches it?
Thanks,
Scott