You are a professional level SQL Sever 2008 Database Administrator in an international corporation named Wiikigo. There is a team of database administrators in your company. SQL Server 2008…

Question

Exhibit

Options

• ATo achieve the goal, the Import and Export Wizard should be utilized to save packages.
• BTo achieve the goal, a direct package configuration should be created for each package.
• CTo achieve the goal, a deployment utility should be created for the SSIS project.
• DTo achieve the goal, an indirect package configuration should be created for all packages.

• A
  13% (4)
• B
  6% (2)
• C
  77% (24)
• D
  3% (1)

Explanation

The first step in deploying packages is to create a deployment utility for an Integration Services project. The deployment utility is a folder that contains the files you need to deploy the packages in an Integration Services project on a different server. The deployment utility is created on the computer on which the Integration Services project is stored. You create a package deployment utility for an Integration Services project by first configuring the build process to create a deployment utility, and then building the project. When you build the project, all packages and package configurations in the project are automatically included. To deploy additional files such as a Fteadme file with the project, place the files in the Miscellaneous folder of the Integration Services project. When the project is built, these files are also automatically included. You can configure each project deployment differently. Before you build the project and create the package deployment utility, you can set the properties on the deployment utility to customize the way the packages in the project will be deployed. For example, you can specify whether package configurations can be updated when the project is deployed. To access the properties of an Integration Services project, right-click the project and click Properties. The following table lists the deployment utility properties. When you build an Integration Services project, a manifest file, qproject name>.SS|SDep|oymentlv1anifest.xmI, is created and added, together with copies of the project packages and package dependencies, to the bintlileployment folder in the project, or to the location specified in the DepIoymentOutputPath property. The manifest file lists the packages, the package configurations, and any miscellaneous files in the project. The content of the deployment folder is refreshed every time that you build the project. This means that any file saved to this folder that is not copied to the folder again by the build process will be deleted. For example, package configuration files saved to the deployment folders will be deleted.

No community discussion yet for this question.