Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution th
at 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 w
ill not appear in the review screen.
You have the following line-of-business solutions:
ERP system
Online WebStore
Partner extranet
One or more Microsoft SQL Server instances support each solution. Each solution has its own product catalog. You have an a
dditional server that hosts SQL Server Integration Services (SSIS) and a data warehouse. You populate the data warehouse with data from each of the line-of-business solutions. The data warehouse does not store primary key values from the individual source
tables.
The database for each solution has a table named
Products
that stored product information. The
Products
table in each database uses a separate and unique key for product records. Each table shares a column named
ReferenceNr
between the databases.
This column is used to create queries that involve more than once solution.
You need to load data from the individual solutions into the data warehouse nightly. The following requirements must be met:
If a change is made to the
ReferenceNr
column in any o
f the sources, set the value of
IsDisabled
to
True
and create a new row in the
Products
table.
If a row is deleted in any of the sources, set the value of
IsDisabled
to
True
in the data warehouse.
Solution: Perform the following actions:
Enable the
Change
Tracking
feature for the
Products
table in the three source databases.
Query the
CHANGETABLE
function from the sources for the deleted rows.
Set the
IsDisabled
column to True on the data warehouse
Products
table for the listed rows.
Does the solution
meet the goal?
A. Yes
B. No
Explanation:
We must check for updated rows, not just deleted rows.
References: https://www.timmitchell.net/post/2016/01/18/getting-started-with-change-tracking-in-sql-server/