Caboodle: Referential Integrity
A lookup column in Caboodle carries the fee ‐3. What should this imply? - ANS-The data
that after populated this row in Caboodle has been deleted from the source or this is the row
with -three as its primary key, for which all lookup columns are also -3. Check the primary
key price for the given row to recognise that is real: non-negative price shows that this
represents deleted statistics within the source.
A row in a Caboodle table has a number one key value of ‐2. What price might be stored in
columns with a facts kind of "Date" for this row that are not lookup columns? - ANS-NULL.
For the row with a primary key of ‐2, lookup columns will store a fee of ‐2, string columns
will shop '*Not Applicable', and all different facts type columns will store NULL.
If a lookup column is null in Clarity, what's going to appear inside the corresponding column
in Caboodle? - ANS-If the research column changed into null inside the source and the SSIS
package deal defines the statistics lineage, then a ‐1 will appear in Caboodle to symbolize
an unspecified value. If the appearance up column's information lineage was now not
described by way of the SSIS bundle that loaded statistics for a selected row, then a ‐2 will
seem in
Caboodle to represent a price that isn't relevant.
Inferred Row - ANS-Placeholder rows which might be added to the destination table while
the lookup column cost does now not have a match in the vacation spot desk
Log into Hyperspace because the Cogito Tools Administrator, open the Patients facts version
in SlicerDicer,
and click on Troubleshoot. What is the reason of the WHERE clause on this facts model? -
ANS-The WHERE clause (WHERE subq.DurableKey > zero) filters out the rows with terrible
long lasting key values from PatientDim. Since these rows do now not represent actual
sufferers, they should now not be protected inside the general count of sufferers inside the
Patients information version.
Referential Integrity - ANS-approach that lookup columns will always have a cost and that
price will find a healthy inside the destination column. When a null or unequalled cost is
loaded into Caboodle staging database, ETL infrastructure assigns a default cost to
corresponding column in the reporting database. A assets of SQL databases with essential
residences-
1. Lookup columns will constantly have a price even supposing the source statistics is null.
2. Lookup column values will constantly have an identical cost within the destination table
column. Even if they're negative, research column values need to discover a match.
Suppose you're developing a report the usage of EncounterFact and ProviderDim that
displays the call of each provider for each come upon. If an come upon's information loads
into EncounterFact, however that company's statistics hasn't been extracted to ProviderDim,
A lookup column in Caboodle carries the fee ‐3. What should this imply? - ANS-The data
that after populated this row in Caboodle has been deleted from the source or this is the row
with -three as its primary key, for which all lookup columns are also -3. Check the primary
key price for the given row to recognise that is real: non-negative price shows that this
represents deleted statistics within the source.
A row in a Caboodle table has a number one key value of ‐2. What price might be stored in
columns with a facts kind of "Date" for this row that are not lookup columns? - ANS-NULL.
For the row with a primary key of ‐2, lookup columns will store a fee of ‐2, string columns
will shop '*Not Applicable', and all different facts type columns will store NULL.
If a lookup column is null in Clarity, what's going to appear inside the corresponding column
in Caboodle? - ANS-If the research column changed into null inside the source and the SSIS
package deal defines the statistics lineage, then a ‐1 will appear in Caboodle to symbolize
an unspecified value. If the appearance up column's information lineage was now not
described by way of the SSIS bundle that loaded statistics for a selected row, then a ‐2 will
seem in
Caboodle to represent a price that isn't relevant.
Inferred Row - ANS-Placeholder rows which might be added to the destination table while
the lookup column cost does now not have a match in the vacation spot desk
Log into Hyperspace because the Cogito Tools Administrator, open the Patients facts version
in SlicerDicer,
and click on Troubleshoot. What is the reason of the WHERE clause on this facts model? -
ANS-The WHERE clause (WHERE subq.DurableKey > zero) filters out the rows with terrible
long lasting key values from PatientDim. Since these rows do now not represent actual
sufferers, they should now not be protected inside the general count of sufferers inside the
Patients information version.
Referential Integrity - ANS-approach that lookup columns will always have a cost and that
price will find a healthy inside the destination column. When a null or unequalled cost is
loaded into Caboodle staging database, ETL infrastructure assigns a default cost to
corresponding column in the reporting database. A assets of SQL databases with essential
residences-
1. Lookup columns will constantly have a price even supposing the source statistics is null.
2. Lookup column values will constantly have an identical cost within the destination table
column. Even if they're negative, research column values need to discover a match.
Suppose you're developing a report the usage of EncounterFact and ProviderDim that
displays the call of each provider for each come upon. If an come upon's information loads
into EncounterFact, however that company's statistics hasn't been extracted to ProviderDim,
