locked
ssis package configurations ? RRS feed

  • Question

  • hi all

        i have one package which was devloped in dev server , and now i want to deploy in prod, maint ...   , now i dont have a option to use environment varaible

         but store i can store config files in sql server table  or  xml at one central  point .....  ( which one is better sql serv or xml)

                                            so if i save all configs in one table will the package loop through all configs .. or do we need to setup ...... ( iwanted that package to execute on all servers(configs) daily)

     

              any suggestions or links will be realy help full 


    Thursday, August 4, 2011 3:19 AM

Answers

  • You need to create "Deployment Utility" for your package. Using that, you can easily deploy your package to different environments.

    I emphasize that you need only ONE config file. and you'll need to configure this file only once per environment, which is at the deployment time (In other words, you don't need to do that each time you want to execute your package). All the configurations are there after deployment.

    Check this post to have  better idea of deployment utility and different options you have.

     


    http://thebipalace.wordpress.com

    • Marked as answer by Eileen Zhao Friday, August 12, 2011 5:52 AM
    Thursday, August 4, 2011 4:07 AM

All replies

  • Hi,

    You don't need to have multiple config files (one for each environment). All you need is a single config file, and change its properties based on the environment you are going to deploy your package to.


    http://thebipalace.wordpress.com

    Thursday, August 4, 2011 3:22 AM
  •   hi

     

       so  i need to change the properties of one config file ..as there are four other servers ..... can i automate this change to happen when i exec package

    Thursday, August 4, 2011 3:59 AM
  • I am not clear about your question, why you want to loop through config files?

    Did you assigned configuration on all packages? did you assigned direct or indirect configuration?

    now what is your problem at deployment machine?


    http://www.rad.pasfu.com
    My Submitted sessions at sqlbits.com
    Thursday, August 4, 2011 4:07 AM
  • You need to create "Deployment Utility" for your package. Using that, you can easily deploy your package to different environments.

    I emphasize that you need only ONE config file. and you'll need to configure this file only once per environment, which is at the deployment time (In other words, you don't need to do that each time you want to execute your package). All the configurations are there after deployment.

    Check this post to have  better idea of deployment utility and different options you have.

     


    http://thebipalace.wordpress.com

    • Marked as answer by Eileen Zhao Friday, August 12, 2011 5:52 AM
    Thursday, August 4, 2011 4:07 AM
  • hi  reza raad

      srry for the confusion

       actually i have one package  developed on one server .... now it should be deployed on 4 other servers ... (i need to run package on all servers every day) ..what is the best way to achive this (i can use every thing except environment variable) ...

    Thursday, August 4, 2011 12:27 PM
  • thank you saeedb

     

              post looks great ..now  i have to try the option of file system deployement ..as i dont have a package store

    Thursday, August 4, 2011 12:30 PM
  • Good.. Let me know if you need more help.
    http://thebipalace.wordpress.com

    Friday, August 5, 2011 1:02 AM