locked
Difference between Package Parameters and Package variables

    Question

  • What is the difference between Package Parameters and Package variables? Thanks in Advance
    Thursday, December 8, 2011 8:14 PM

All replies

  •  

    One difference is scope , Package variables are limited to package but  "parameters at package as well as project scopes. A package parameter would be scoped and be available for the respective package execution while a project parameterwould be available for the execution for any package within the project."

     

    Check this link for details.

     

    http://blogs.msdn.com/b/mattm/archive/2011/07/16/configuring-projects-and-packages-using-parameters.aspx

     

     

     

    Thanks

     

    Aamir

     


    http://sqlage.blogspot.com/
    Thursday, December 8, 2011 9:19 PM
  • Any other differences?
    Tuesday, December 13, 2011 10:20 PM
  • Parameters are configurable after the deployment this is the main reson u should use parameter, if u want to configure it at run time .after the deployment with in catalog you can reassing your parameter's value.
    Wednesday, December 14, 2011 5:28 AM
  • What is the difference between Package Parameters and Package variables? Thanks in Advance


    Parameters are configurable values.

    For example: In Denali, one can assign all Execution Timeouts of Execute SQL Tasks to have a timeout value of 45 seconds (This is called as paraterized tasks)

    Variables on the other hand are mere storage objects which can be used to store a value or used by package to perform computational tasks

    For example: Path of working directory where the daily ETL loads arrive. This path will be used say in a FEL(For each loop) to loop for any files matching a pattern. 


    Please vote as helpful or mark as answer, if it helps
    Tuesday, January 10, 2012 6:10 PM
  • Package Parameters can be configured in the execute package task on the control flow.  A typcial scenario is to dynamically compute a value for a variable, then assign that value to a package parameter for use in the package being called by an execute package task.  This is how the new execute package task with project reference is designed to work.

     

    Project parameter values remain constant throughout the project execution, and are available to all packages in a project.  You cannot assign the value of a project parameter inside the execute package task.

    • Proposed as answer by Venkataraman R Wednesday, January 18, 2012 6:04 AM
    Tuesday, January 17, 2012 4:07 PM