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
6 months agoDerrick
6 months agoJames
5 months agoAshley
5 months agoBea
6 months agoDeandrea
6 months agoErnest
5 months agoMelvin
5 months agoCarylon
6 months agoLea
6 months agoJolanda
6 months agoFrance
6 months agoArlene
6 months agoMozell
6 months agoJeannetta
7 months agoZona
6 months agoJuliann
6 months agoErnie
6 months agoDelpha
6 months agoTammara
6 months agoLouvenia
6 months agoJennifer
7 months agoBulah
6 months agoRegenia
7 months agoNicolette
7 months agoBea
7 months agoLea
7 months agoNicolette
7 months agoTheola
8 months agoGaynell
8 months agoEleonore
8 months agoTheola
8 months agoGaynell
8 months agoEleonore
8 months ago