What are some best practices for writing SQLScript for use with calculation views? Note: There are 2 correct answers to this question.

• A.Control the flow logic using IF-THEN-ELSE conditions.
• B.Choose declarative language instead of imperative language.
• C.Break up large statements by using variables.
• D.Use dynamic SQL.

Comment: *

Name: *

Email: *

Verification: *

You want to join two tables in a calculation view. Why do you use a non-equi join?

• A.Join columns need to be ignored when NOT requested by the query.
• B.The join condition is not represented by matching values.
• C.The number of joined columns is different in each table.
• D.Join columns have different data types.

Comment: *

Name: *

Email: *

Verification: *

What are some best practices when developing calculation views? Note: There are 2 correct answers to this question.

• A.Model star schemas using a sequence of join nodes.
• B.Avoid defining joins on calculated columns.
• C.Include all data flow logic within one calculation view.
• D.Aggregate at the lowest possible node.

Comment: *

Name: *

Email: *

Verification: *

What can you identify using Performance Analysis mode? Note: There are 2 correct answers to this question.

• A.Information about join cardinality
• B.Expected memory consumption
• C.Joins that are defined on calculated columns
• D.Usage statistics of the calculation view

Comment: *

Name: *

Email: *

Verification: *

You have generated a calculation view properties file. What does it contain?

• A.Descriptions of all objects defined in a calculation view
• B.Documentation to support the calculation view
• C.All settings defined in a calculation view
• D.Dependencies between calculation views

Comment: *

Name: *

Email: *

Verification: *