|
Data Warehouse |
|
|
[SSIS] |
|
|
Questions: |
Notes: |
|
How do you apply configurations to a package? |
Use a package configuration to override selected property values stored in a separate file or configuration resource. Typically, this is used to apply properties, such as file paths or connection strings, that would need to be changed when the package is moved to a test or production environment. |
|
What are the methods to manually execute a package? |
The manual method to execute a package is to locate the package in SQL Server Management Studio Integration Services, right-click the package, and choose Run Package from the menu. This might be simple, but it’s not convenient. |
|
What are the methods to automatically execute a package? |
A package can be schedule to run by the server. Typically, you do this by using the SQL Server Agent with a simple command-line script. Using the Agent, the job can be scheduled to run at set intervals. Alerts can be set up to send e-mail, page, or log entries upon success or failure. |
|
How do you monitor Package Execution? |
Package execution can be monitored by auditing by using three methods, which include active monitoring in SSMS, console reporting in the command window, and viewing execution logs. A number of logging options are available that can be enabled in Execute Package Utility. |
|
What are Transactions for? |
Transactions are used to maintain data integrity by ensuring that a database remains in a consistent state even if a package fails.
They accomplish this by binding the database actions that tasks perform into units, which either succeed or fail together. |
|
What can Transactions be used on? |
Transactions can be enabled for all SSIS container types, including tasks, containers, and packages. |
|
How do you configure Transactions? |
You configure transactions by using the container’s TransactionOption property, which is set in the SSIS design environment. |
|
What is Not Supported? |
Not Supported is where the container does not start a transaction and will not join an existing transaction even if it has already started. |
|
What is Supported? |
Supported is where the container does not start a transaction but will join an existing transaction that has already started. |
