Northern Trail Outfitters (NTO) wants to capture a list of customers that have bought a particular product. The solution architect has recommended to create a custom object for product, and to create a lookup relationship between its customers and its products.
Products will be modeled as a custom object (NTO_ Product__ c) and customers are modeled
as person accounts. Every NTO product may have millions of customers looking up a single product, resulting in a lookup skew.
What should a data architect suggest to mitigate Issues related to lookup skew?
creating multiple similar products and distributing the skew across those products can be a way to mitigate issues related to lookup skew. The article explains that lookup skew happens when a very large number of records are associated with a single record in the lookup object, and this can cause record locking and performance issues. The article suggests creating multiple copies of the same product record and assigning different child records to each copy, so that the number of child records per parent record is reduced.
Dusti
10 months agoDerrick
10 months agoJames
10 months agoAshley
10 months agoBea
10 months agoDeandrea
10 months agoErnest
10 months agoMelvin
10 months agoCarylon
10 months agoLea
10 months agoJolanda
11 months agoFrance
10 months agoArlene
10 months agoMozell
10 months agoJeannetta
11 months agoZona
10 months agoJuliann
10 months agoErnie
10 months agoDelpha
11 months agoTammara
11 months agoLouvenia
11 months agoJennifer
11 months agoBulah
11 months agoRegenia
11 months agoNicolette
11 months agoBea
12 months agoLea
12 months agoNicolette
12 months agoTheola
1 years agoGaynell
1 years agoEleonore
1 years agoTheola
1 years agoGaynell
1 years agoEleonore
1 years ago