Shulou(Shulou.com)06/01 Report--

Parameters can be used in Project Deployment Model, not in Package Deployment Model. Under Package Deployment Model, use Package Configurations to pass property values; under Project Deployment Model, use Parameters to pass values.

1,Parameters and Package Deployment Model

In general, if you are deploying a package using the package deployment model, you should use configurations instead of parameters.

When you deploy a package that contains parameters using the package deployment model and then execute the package, the parameters are not called during execution. If the package contains package parameters and expressions within the package use the parameters, the resulting values are applied at runtime. If the package contains project parameters, the package execution may fail.

2Magical parameters are divided into two Level,Project Level and Package Level, and the parameters value of both level is stored in project files.

Project Parameters values and Packages parameters values are stored in configurations in the project file .

Integration Services (SSIS) parameters allow you to assign values to properties within packages at the time of package execution. You can create project parameters at the project level and package parameters at the package level. Project parameters are used to supply any external input the project receives to one or more packages in the project. Package parameters allow you to modify package execution without having to edit and redeploy the package.

One, Package Parameter

1. Under Project Deployment Model, open the parameters tab and New a Package Parameter,Parameter whose name is ParameterA.

Sensitive: sensitive information that needs to be encrypted

Required: must be provided, otherwise an error will occur

Property

Description

Name

The name of the parameter.

Data type

The data type of the parameter.

Default value

The default value for the parameter assigned at design time. This is also known as the design default.

Sensitive

Sensitive parameter values are encrypted in the catalog and appear as a NULL value when viewed with Transact-SQL or SQL Server Management Studio.

Required

Requires that a value, other than the design default, is specified before the package can execute.

Description

For maintainability, the description of the parameter. In SQL Server Data Tools (SSDT), set the parameter description in the Visual Studio Properties window when the parameter is selected in the applicable parameters window.

2,Add parameters to Configurations

3,Set Parameter Values After the Project Is Deployed

The Deployment Wizard allows you to set server default parameter values when you deploy your project to the catalog. After your project is in the catalog, you can use SQL Server Management Studio (SSMS) Object Explorer or Transact-SQL to set server default values.

To set server defaults with SSMS Object Explorer:

Select and right-click the project under the Integration Services node.

Click Properties to open the Project Properties dialog window.

Open the parameters page by clicking Parameters under Select a page.

Select the desired parameter in the Parameters list. Note: The Container column helps distinguish project parameters from package parameters.

In the Value column, specify the desired server default parameter value.

To set server defaults with Transact-SQL, use the catalog.set_object_parameter_value (SSISDB Database) stored procedure. To view current server defaults, query the catalog.object_parameters (SSISDB Database) view. To clear a server default value, use the catalog.clear_object_parameter_value (SSISDB Database) stored procedure.

There are two methods available on MSDN, one is to use SSMS to modify, the other is to use TSQL statement to modify

3.1 use SSMS to modify

Select integration Services Catalogs, right-click TestISProjects to open Configure

Click. To set the value of the parameter

Second, Project Parameter

1. Under the Project view, open Project.params and create a Parameter for project level, named ProjectParameter_A.

2, add Project Parameter to configurations

3. After publishing to Sql server, modify the default value of Project parameter.

Three, Use of package and project parameters

Parameters are useful for providing runtime values to properties during a package execution. Hence, in a way they replace the concept of configurations that we had for SSIS packages.

Package parameters are useful for providing values to specific package executions. As they are package scope, they would only be available to the package in which they were created.

Project parameters are available to all the packages in a project. They are useful for configuring values which can be shared between packages. For instance if you wanted to have a single parameter containing a server name to be used by multiple packages, then Project Parameters will be useful for you.

You can use a parameter anywhere in an expression by referring it using the following syntax:

@ [$:]

The evaluation order is similar to using a variable in an expression and then executing a package. Hence, the value gets evaluated and assigned to the property at Validation phase.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.