Microsoft Implementing Data Models and Reports with Microsoft SQL Server (070-466日本語版) - 070-466日本語 Exam Practice Test

Explanation:
Box 1:

Box 2:

Box 3:

Note:
* you can use the Linked Object Wizard to add a measure group from another database
* You can use the Linked Object Wizard to either link to or import cubes, dimensions, measure groups, calculations, and Key Performance Indicators (KPIs). You can link to or import these items from another database on the same server or from a database on a remote server
* The Linked Object Wizard guides you through the following steps:
Selecting the Analysis Services data source from which to link or import objects.
Selecting the objects from which to link or import.
Saving the changes.
Create or modify a linked measureUse SQL Server Data Tools to create a linked measure group.
* Finalize any modifications to the original measure group now, in the source cube, so that you don't have to recreate the linked measure groups later in subsequent cubes. You can rename a linked object, but you cannot change any other properties.
* In Solution Explorer, double-click the cube to which you are adding the linked measure group. This step opens the cube in Cube Designer.
* In Cube Designer, in either the Measures pane or Dimensions pane, right-click anywhere in either pane, then select New Linked Object. This starts the Linked Object Wizard.
* On the first page, specify the data source. This step establishes the location of the original measure group. The default is the current cube in the current database, but you can also choose a different Analysis Services database.
* On the next page, choose the measure group or dimension you want to link.
Dimensions and Cube objects, such as measure groups, are listed separately.
Only those objects not already present in the current cube are available.
* Click Finish to create the linked object. Linked objects appear in the Measures and Dimensions pane, indicated by the link icon.
Ref: http://msdn.microsoft.com/en-us/library/ms174899(v=sql.110).aspx

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

Explanation:
Box 1:

Box 2:

Box 3:

Note:
* You can use the Linked Object Wizard to either link to or import cubes, dimensions, measure groups, calculations, and Key Performance Indicators (KPIs). You can link to or import these items from another database on the same server or from a database on a remote server
* On the Select a Data Source page of the Linked Object Wizard, choose the Analysis Services data source or create a new one.
* On the Select Objects page of the wizard, choose the dimensions you want to link to in the remote database. You cannot link to linked dimensions in the remote database.
* Incorrect:
The Business Intelligence Wizard can guide you through some or all the following steps:
Define time intelligence for cubes.
Define account intelligence for cubes and dimensions.
Define dimension intelligence for cubes and dimensions.
Define unary operators for cubes.
Set custom member formulas for cubes and dimensions.
Specify attribute ordering for dimensions.
Enable dimension writeback for dimensions.
Define semi-additive behavior for cubes.
Define currency conversion for cubes.

Explanation:
Box 1:

Box 2:

Box 3:

Note:
* Processing mode has two possible options.
Regular. This is the default setting. When set to regular, partitions will be available to users after data has been loaded and aggregations are created completely.
Lazy Aggregations. When set to lazy aggregations, partitions will be available to user queries immediately after data has been loaded. Aggregations will be created as a separate background process while users start to query the partition.
* Lazy processing performs the task of building indexes and aggregations for dimensions and measure group partitions at a lower priority to reduce foreground processing time and to allow users to query the cube sooner. For lazy processing to occur, you must switch the ProcessingMode = LazyAggregations of your measure group partitions; by default this value is Regular (lazy processing is turned off). When processing a dimension with flexible aggregations such as parent-child or virtual dimension by using the processing enumeration of ProcessUpdate (such as to take into account of member name or hierarchy changes), lazy processing is initiated to ensure that the aggregations are rebuilt on the associated measure group partitions.
* Configure Lazy Processing for the cube, measure group, or partition. If you configure Lazy Processing, the dropped aggregations are recalculated as a background task. While the flexible aggregations are being recalculated, users can continue to query the cube (without the benefit of the flexible aggregations). While the flexible aggregations are being recalculated, queries that would benefit from the flexible aggregations run slower because Analysis Services resolves these queries by scanning the fact data and then summarizing the data at query time. As the flexible aggregations are recalculated, they become available incrementally on a partition-by-partition basis. For a given cube, Lazy Processing is not enabled by default. You can configure it for a cube, measure group, or partition by changing the ProcessingMode property from Regular to LazyAggregations. To manage Lazy Processing, there are a series of server properties such as the LazyProcessing \ MaxObjectsInParallel setting, which controls the number of objects that can be lazy processed at a given time. By default it is set to 2. By increasing this number, you increase the number of objects processed in parallel; however, this also impacts query performance and should therefore be handled with care.
* Incorrect: With Bring Online Immediately enabled, during cache refresh all queries are directed to the relational source database to retrieve the latest data for end users. While this provides users with refreshed data, it can also result in reduced query performance given that Analysis Services needs to redirect queries to the relational source database.

Explanation:
Box 1: Open Report Manager and then click the shared dataset.
We should use Report Manager (not SharePoint Central Administration).
Box 2: Select the Caching page and then click the Cache shared dataset checkbox.
We set up caching.
Box 3: Select the Expire the cache on the following schedule option and then select the Shared Schedule option.
We configure caching further.
Box 4: From the combo box, select the shared schedule and then click Apply.
Finally we define scheduling.
Note on caching:
To open the Caching properties page for a shared dataset
* Open Report Manager, and locate the report for which you want to configure shared dataset properties.
* Point to the shared dataset, and click the drop-down arrow.
* In the drop-down list, click Manage. The General properties page for the report opens.
* Click the Caching tab.
Options include:
Cache shared dataset (Box 2 above)
Places a temporary copy of the data in a cache when a user first opens a report that uses this shared dataset. Subsequent users who run the report within the caching period receive the cached copy of the data. Caching usually improves performance because the data is returned from the cache instead of running the dataset query again.
Expire the cache on the following schedule (box 3 above)
Schedule the time when the cached data is no longer valid and is removed from the cache.
The schedule can be a shared schedule or one that is specific for only the current shared dataset.