70-463 · Question #8
You develop and deploy a SQL Server Integration Services (SSIS) package. The package is stored in the file system. You need to execute the package without importing it to the SSIS server. What…
The correct answer is B. dtexec D. SQL Server Agent. This question tests which tools can execute an SSIS package stored on the file system without first importing it into the SSIS catalog.
Question
You develop and deploy a SQL Server Integration Services (SSIS) package. The package is stored in the file system. You need to execute the package without importing it to the SSIS server. What should you use to execute the package? (Each correct answer presents a complete solution. Choose all that apply.)
Options
- Acatalog.start_package
- Bdtexec
- CSQL Server Management Studio
- DSQL Server Agent
How the community answered
(39 responses)- A5% (2)
- B92% (36)
- C3% (1)
Why each option
This question tests which tools can execute an SSIS package stored on the file system without first importing it into the SSIS catalog.
catalog.start_package is a stored procedure in the SSISDB catalog and can only execute packages that have been deployed to the catalog, not file system packages.
dtexec is the command-line utility that can execute SSIS packages directly from the file system using the /FILE switch, requiring no catalog import.
SQL Server Management Studio's SSIS execution interface in the Object Explorer requires the package to be imported into the SSIS catalog (SSISDB); it cannot directly execute arbitrary file system packages.
SQL Server Agent can be configured with a job step of type 'SQL Server Integration Services Package' pointing to a file system path, allowing execution without catalog import.
Concept tested: Executing SSIS packages from the file system without catalog import
Source: https://learn.microsoft.com/en-us/sql/integration-services/packages/run-integration-services-ssis-packages
Topics
Community Discussion
No community discussion yet for this question.