You need to ensure that the project is deployed to the SSIS catalog on the production server

You are developing a SQL Server Integration Services (SSIS) project that copies a large amount of
rows from a SQL Azure database, The project uses the Package Deployment Model. This project is
deployed to SQL Server on a test server. You need to ensure that the project is deployed to the SSIS
catalog on the production server. What should you do?

You are developing a SQL Server Integration Services (SSIS) project that copies a large amount of
rows from a SQL Azure database, The project uses the Package Deployment Model. This project is
deployed to SQL Server on a test server. You need to ensure that the project is deployed to the SSIS
catalog on the production server. What should you do?

A.
Add an OnError event handler to the SSIS project.

B.
Use an msi file to deploy the package on the server.

C.
Open a command prompt and run the gacutil command.

D.
Open a command prompt and run the dtutil /copy command.

E.
Open a command prompt and run the dtexec /rep /conn command.

F.
Open a command prompt and run the dtexec /dumperror /conn command.

G.
Open a command prompt and execute the package by using the SQL Log provider and running the
dtexecui.exe utility.

H.
Create a reusable custom logging component and use it in the SSIS project.

I.
Configure the SSIS solution to use the Project Deployment Model.

J.
Configure the output of a component in the package data flow to use a data tap.
K.
Run the dtutil command to deploy the package to the SSIS catalog and store the configuration in
SQL Server.

Explanation:
Reference:
http://msdn.microsoft.com/en-us/library/hh231102.aspx
http://msdn.microsoft.com/en-us/library/hh213290.aspx
http://msdn.microsoft.com/en-us/library/hh213373.aspx



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Google

Google

Just beneath, are several absolutely not related web pages to ours, however, they are surely really worth going over.