|
Data Warehouse |
|
|
[SSIS] |
|
|
Questions: |
Notes: |
|
What is the difference between running a package in the SSIS development platform and in a production server? |
The package designer and development platform does a good job of emulating true package execution, but it isn’t the same for at least two reasons. In the designer, a package runs with debugging checks and additional overhead that use up memory and CPU cycles, which can throttle back performance and capabilities. In a deployed server environment, SSIS will dedicate more resources to package execution, buffer space, memory allocation, and parallel processing. |
|
Are packages run manually or automatically on the server? |
After a package has been deployed to the server, it can be executed manually or scheduled to run automatically. |
|
What is a Deployment Manifest File for? |
An SSIS project can be configured to prepare packages for server deployment by using a deployment manifest file. This is a convenient method to deploy the packages in a project. |
|
How do you prepare packages for deployment? |
You prepare packages for deployment you use the Package Installation Wizard to make changes to an existing project in order to prepare packages for deployment. Setting the project properties to create a deployment utility instructs BIDS to generate a folder containing copies of all packages ready for development along with a deployment manifest file when choosing the Build option. |
|
What are two ways of securing a deployment package? |
You can protect a package in two ways: by encrypting sensitive information stored in the package definition file and by controlling who has the ability to run or make changes to a deployed package. |
|
What is Package Password Protection? |
You can use password protection to prevent modification and deployment. The development environment will prompt for a password when attempting to open the package file.
The real value of password protection is when the password is used in conjunction with package encryption.d |
