Hi All, Hope you can help. We have an events system that uses a number of tables to display the event information with. In order to populate these tables we have a requirement to upload the data using CSV file format. In order to achieve this I wrote a second set of tables to contain the imported data and a script which would then run through each of the imported events and import them into the target tables. CSV Files: events.csv events-bookingoptions.csv events-session.csv Import Tables: ImportEvents. ImportEventBookingOptions. ImportEventSession. LoadHistory. (Table to manage the imported data into ImportEvents, contains, date, status, name, message). Target Tables: Events EventBookingOptions EventSession. Script: sp_TransferFromImportTablesToTargetTables. Database Staging/Production Server There are two instances of SQL server on one server. One for Staging(default), and one for Production - Please Note! They both carry the same set of databases, however a differing permission set. Packages. In order to support the import we have created 3 packages, one for each file and table and a sql job which will run these packages in order and then the relevant script to transfer the data from the imports table to the targets table. The system works fine on our local server and the staging server however when we try and run the job on the production server we get issues, where the package is trying to connect to the default (staging)instance on the server. We have used a configuration manager, specifying the connection strings in a XML file, for the source (CSV files) and the destination (serverx\Staging, server\Production). Has anyone found a similar problem? <please let me know if you need any more details, been on this for 2 days!!>With Kinds Regard, SK.

what is the error that you are getting. My first guess would be authentication problem.My Blog | Ask Me

yes its an authentication problem, because it is trying to connect to the default database (staging).With Kinds Regard, SK.

yes its an authentication problem, because it is trying to connect to the default database (staging). With Kinds Regard, SK. In that case you need to provide the proper credentials and the package should work. Whenever the package works in any one environment and not the other be sure that the issue is not with the package but the environment.My Blog | Ask Me

The error is because through the logs, i can see the package trying to access the default database (Staging) on the same server as the required database (Production) on the same server. We have a differant set of credentials for each of the servers. However we want to run on the production instance of ssis.With Kinds Regard, SK.

How did you deploy and set the package to run? I assume somewhere the config does not get applied.Arthur My Blog