nerdexam
Microsoft

MB6-704 · Question #14

You have two tables named Tablel and Table2. There is a many to one relationship between Table2 and Tablel. You discover that following X++ statement is very slow to execute; Tablelfield cannot have…

The correct answer is C. Aunique index in table 1Field and a non-unique index in table2refField. Put a unique index on the one-side field of the relation, that is on Table1. Put a non-unique index on the many-side field of the relation, that is on Table2.

inventory configuration

Question

You have two tables named Tablel and Table2. There is a many to one relationship between Table2 and Tablel. You discover that following X++ statement is very slow to execute; Tablelfield cannot have duplicate data in Table 1 You need to reduce the amount of time it takes for the code to execute. What should you create?

Options

  • AAunique index in table 1Field and a unique index in table2.refField
  • BAnon-unique index in table 1Field and a unique index in table2.refField
  • CAunique index in table 1Field and a non-unique index in table2refField
  • DAnon-unique index in table 1Field and a non-unique index in table2refField

How the community answered

(22 responses)
  • A
    5% (1)
  • B
    5% (1)
  • C
    77% (17)
  • D
    14% (3)

Explanation

Put a unique index on the one-side field of the relation, that is on Table1. Put a non-unique index on the many-side field of the relation, that is on Table2.

Topics

#database indexes#query optimization#unique index#table relationships

Community Discussion

No community discussion yet for this question.

Full MB6-704 Practice