MB6-704 · Question #73
You have a table named VendTable that contains a field named MainContactWorker. MainContactWorker is the reference Recid. Many records in the VendTable table have the same value for…
The correct answer is B. A surrogate key that is used as the primary index. For new tables the default is a primary key based on the RecId field. This is represented as the surrogate key in the user interface. PrimaryIndex: contains the surrogate key plus every index on the table that has its AlternateKey property set to Yes. Note: If you store…
Question
You have a table named VendTable that contains a field named MainContactWorker. MainContactWorker is the reference Recid. Many records in the VendTable table have the same value for MainContactWorker. Users frequently search for data in the VendTable table based on the MainContactWorker field. You need to ensure that when the users create queries that include the MainContactWorker field in the where clause, the query results are returned in the least amount of time possible. What should you create in VendTable?
Options
- AA unique index in MainContactWorker
- BA surrogate key that is used as the primary index
- CA primary index for MainContactWorker
- DA non-unique index in MainContactWorker
How the community answered
(41 responses)- A5% (2)
- B83% (34)
- C2% (1)
- D10% (4)
Explanation
For new tables the default is a primary key based on the RecId field. This is represented as the surrogate key in the user interface. PrimaryIndex: contains the surrogate key plus every index on the table that has its AlternateKey property set to Yes. Note: If you store surrogate foreign key values in your tables, you will have to correctly work with these values in your Enterprise Portal integration. This involves creating a reference data source to link to the data that is accessed by the surrogate foreign key. It can also include using the AxReferenceField to access the surrogate foreign key value.
Topics
Community Discussion
No community discussion yet for this question.