Microsoft Designing Business Intelligence Solutions with Microsoft SQL Server (70-467日本語版) - 70-467日本語 Exam Practice Test

Explanation
Box 1: Connect to the SSISDB database.
Box 2:

Box 3: Execute the query
Note:
* execution_component_phases
Displays the time spent by a data flow component in each execution phase.
* The following example uses the catalog.execution_component_phases view to find the total amount of time that a specific package has spent executing in all phases (active_time), and the total elapsed time for the package (total_time).
use SSISDB
select package_name, task_name, subcomponent_name, execution_path,
SUM(DATEDIFF(ms,start_time,end_time)) as active_time,
DATEDIFF(ms,min(start_time), max(end_time)) as total_time
from catalog.execution_component_phases
where execution_id = 1841
group by package_name, task_name, subcomponent_name, execution_path
order by package_name, task_name, subcomponent_name, execution_path
* catalog.executables
This view displays a row for each executable in the specified execution.
An executable is a task or container that you add to the control flow of a package.
*(incorrect) catalog.executions (SSISDB Database)
Displays the instances of package execution in the Integration Services catalog. Packages that are executed with the Execute Package task run in the same instance of execution as the parent package.
This view displays a row for each instance of execution in the catalog.
* (incorrect) catalog.operation_messages
Displays messages that are logged during operations in the Integration Services catalog.
This view displays a row for each message that is logged during an operation in the catalog. The message can be generated by the server, by the package execution process, or by the execution engine.
Reference: catalog.execution_component_phases
Reference: catalog.executables

Explanation

Explanation: Only visible for PassTestking members. You can sign-up / login (it's free).

Explanation

http://msdn.microsoft.com/en-us/library/ms175646.aspx
Low Latency MOLAP
Detail data and aggregations are stored in multidimensional format. The server listens for notifications of changes to the data and switches to real-time ROLAP while MOLAP objects are reprocessed in a cache. A silence interval of at least 10 seconds is required before updating the cache. There is an override interval of 10 minutes if the silence interval is not attained. Processing occurs automatically as data changes with a target latency of 30 minutes after the first change.
This setting would typically be used for a data source with frequent updates when query performance is somewhat more important than always providing the most current data. This setting automatically processes MOLAP objects whenever required after the latency interval. Performance is slower while the MOLAP objects are being reprocessed.

Explanation: Only visible for PassTestking members. You can sign-up / login (it's free).