Create simple XML Configuration File Store User ID & Password AS400 Login

• Welsh Corgi

  SSC Guru

  Points: 116520

  More actions

  April 5, 2012 at 11:29 am

  #143294

  I need to create a simple Configuration File Store the User ID & Password of an AS400 Login.

  I previously posted a more general question but I could not find my post.

  I followed an article step by step which involved creating an environmental variable but it corrupted my package.

  I need something very simple so that the package references the Configuration File and I can run the job using SQL Server Agent with my AS400 Credentials.

  Any help would be greatly appreciated.

  For better, quicker answers on T-SQL questions, click on the following...
  http://www.sqlservercentral.com/articles/Best+Practices/61537/

  For better answers on performance questions, click on the following...
  http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

• Orlando Colamatteo

  SSC Guru

  Points: 182293

  More actions

  April 5, 2012 at 4:22 pm

  #1469892

  Was this your more general post?

  There are no special teachers of virtue, because virtue is taught by the whole community.
  --Plato

• Welsh Corgi

  SSC Guru

  Points: 116520

  More actions

  April 5, 2012 at 4:55 pm

  #1469908

  I watched the video. I was a little distracted.

  I'm think I know the basic steps but I'm a little confused on what I have to do.

  Thanks.

  For better, quicker answers on T-SQL questions, click on the following...
  http://www.sqlservercentral.com/articles/Best+Practices/61537/

  For better answers on performance questions, click on the following...
  http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

• Orlando Colamatteo

  SSC Guru

  Points: 182293

  More actions

  April 5, 2012 at 9:13 pm

  #1469949

  When you have the SSIS package open in BIDS, right click some empty space on the Control Flow design surface and choose Package Configurations. From there you can choose XML and a location for the dtsConfig file. Pretty much every property of every object in the package, including variables and connection managers, is "mappable" to an entry in the dtsConfig file. Experiment with it. The more boxes you check the more entries in the dtsConfig file. Once you create the file open it in notepad. I think you'll find them to be quite useful towards avoiding having to hard code configuration data directly into the package.

  Storing your config data in a table is also a great alternative to storing it in a config file. I have used both methods in different shops. The video shows you how to do both if I remember correctly.

  The method aside, my goal is to make all my packages portable from one environment to another, where only a config file or a table entry would need to change when moving the package, and never the code of the SSIS package itself.

  There are no special teachers of virtue, because virtue is taught by the whole community.
  --Plato