070-767 試験問題を無料オンラインアクセス

You are the administrator of a database that hosts tables for a data warehouse.
The table named Fact1 has data from the start of calendar year 2011 through the end of 2017. The table contains at least 20 million rows of data for each year. You create the table by running the following Transact-SQL statement:
CREATE PARTITION FUNCTION PartitionFunc-Fact1(SMALLINT)
AS RANGE LIFT VALUES(2012, 2013, 2014, 2015)
You need to modify the partition function so that rows for each calendar year are in a separate partition. You must also move all data prior to 2014 to another table named Fact1_old.
How should you complete the Transact-SQL statement? To answer, select the appropriate Transact-SQL segment in the dialog box in the answer area.
NOTE: Each correct selection is worth one point.

正解：

Explanation

References:
https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-partition-function-transact-sql
https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-table-transact-sql

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer chokes, but the text of the scenario is exactly the same in each question in the series.
Start of repeated scenario
Contoso. Ltd. has a Microsoft SQL Server environment that includes SQL Server Integration Services (SSIS), a data warehouse, and SQL Server Analysis Services (SSAS) Tabular and multi-dimensional models.
The data warehouse stores data related to your company sales, financial transactions and financial budgets. All data for the data warehouse originates from the company s business financial system.
The data warehouse includes the following tables:

The company plans to use Microsoft Azure to store older records from the data warehouse. You must modify the database to enable the Stretch Database capability.
Users report that they are becoming confused about which city table to use for various queries. You plan to create a new schema named Dimension and change the name of the dbo.diamension_city table to Diamension.city. Data loss is not permissible, and you must not leave traces of the old table in the data warehouse.
The fact. Transaction table has measures named RawCost and Totaisale that calculate the wholesale cost of materials. You plan to create a measure that calculates the profit margin based on the two existing measures.
You must implement a partitioning scheme for the fact.Transaction table to move older data to less expensive storage. Each partition will store data for a single calendar year, as shown in the exhibit (Click the Exhibit button.) You must align the partitions.

You must improve performance for queries against the fact.Transaction table. You must implement appropriate indexes and enable the Stretch Database capability.
End of repeated scenario
You need to create the ProfitMargin measure for the fact. Transaction table.
How should you complete the MDX statement? To answer, select the appropriate MDX segments in the answer area.

正解：

Note: This question is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question in the series. Each question is independent of the other questions in this series. Information and details provided in a question apply only to that question.
You are developing a Microsoft SQL Server Integration Services (SSIS) package.
You need to use XPath to extract information from documents.
Which SSIS Toolbox item should you use?

• A.Merge Join
• B.XML task
• C.CDC Splitter
• D.Merge
• E.Fuzzy Grouping
• F.CDC Control task
• G.Union All

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the text of the scenario is exactly the same in each question in this series.
You have a Microsoft SQL Server data warehouse instance that supports several client applications.
The data warehouse includes the following tables: Dimension.SalesTerritory, Dimension.Customer, Dimension.Date, Fact.Ticket, and Fact.Order. The Dimension.SalesTerritory and Dimension.Customer tables are frequently updated. The Fact.Order table is optimized for weekly reporting, but the company wants to change it to daily. The Fact.Order table is loaded by using an ETL process. Indexes have been added to the table over time, but the presence of these indexes slows data loading.
All data in the data warehouse is stored on a shared SAN. All tables are in a database named DB1. You have a second database named DB2 that contains copies of production data for a development environment. The data warehouse has grown and the cost of storage has increased. Data older than one year is accessed infrequently and is considered historical.
You have the following requirements:
* Implement table partitioning to improve the manageability of the data warehouse and to avoid the need to repopulate all transactional data each night. Use a partitioning strategy that is as granular as possible.
* Partition the Fact.Order table and retain a total of seven years of data.
* Partition the Fact.Ticket table and retain seven years of data. At the end of each month, the partition structure must apply a sliding window strategy to ensure that a new partition is available for the upcoming month, and that the oldest month of data is archived and removed.
* Optimize data loading for the Dimension.SalesTerritory, Dimension.Customer, and Dimension.Date tables.
* Incrementally load all tables in the database and ensure that all incremental changes are processed.
* Maximize the performance during the data loading process for the Fact.Order partition.
* Ensure that historical data remains online and available for querying.
* Reduce ongoing storage costs while maintaining query performance for current data.
You are not permitted to make changes to the client applications.
You need to configure data loading for the tables.
Which data loading technology should you use for each table? To answer, select the appropriate options in the answer area.

正解：

Explanation

Scenario: The Dimension.SalesTerritory and Dimension.Customer tables are frequently updated Optimize data loading for the Dimension.SalesTerritory, Dimension.Customer, and Dimension.Date tables.
Box 1: Change Tracking
Box 2: Change Tracking
Box 3: Temporal Table
Temporal Tables are generally useful in scenarios that require tracking history of data changes.
We recommend you to consider Temporal Tables in the following use cases for major productivity benefits.
* Slowly-Changing Dimensions
Dimensions in data warehousing typically contain relatively static data about entities such as geographical locations, customers, or products.
References:
https://docs.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-usage-scenarios

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You are the administrator of a Microsoft SQL Server Master Data Services (MDS) instance. The instance contains a model named Geography and a model named customer. The Geography model contains an entity named countryRegion.
You need to ensure that the countryRegion entity members are available in the customer model.
Solution: Configure an entity sync relationship to replicate the CountryRegion entity.
Does the solution meet the goal?

• A.No
• B.Yes