No that intersection when we are talking about some of the best practices that we can implement in data
management.
The next topic that we are going to talk about is a day desk.
So what does data skew data skew is basically a condition of having an appropriate ratio of records
to a parent to record or to an owner.
Basically that is out of balance.
So that is called us a data skew.
We can cite many examples for that.
Some of the common scenarios that we encountered as you know we may have several inactive customers.
So what we may do is we may assign all of the inactive customers to the V.P. order director and over
time what may happen as of the V.P. He or she may have over like a hundred key accounts that they own.
All right.
They own meaning basically that was assigned to them but at the same time our sales force and on an
average may have around 2000 or 3000 active calls.
So basically if you see there is a enormous difference.
That is like this 50 fold difference in ownership patterns.
It makes it harder for the salesforce query optimizer to know exactly like the number of records owned
by the person and how to actually get to the records you want more efficiently and under a situation
that I can call this up say for example you have many old contacts in your system.
So all context meaning contacts that have not been active for quite long already have not contacted
that contact for quite long.
Ah there have been more transactions or activities in those contacts.
So if you have so many old contacts in your system and you one day you decide to create an account record
and you map all the old contacts with a contract card.
All right.
So this process of mapping to many numerous contacts to one single account record even this will cost
data skew.
So this account this single account direct card that will kill the system that is skewed the way optimizer
thinks about the underlying data and it does also negatively impacts your sales force.
And it also negatively impacts sales force from being as efficient as possible.
So this is the concept of data SKU.
So as a basic rule of thumb What do you want to notice at any point of time.
Do not have more than 10000 thousand records for a single parent card auto owner no one card owning
basically more than ten thousand records make class a data issue and may lead to this data skew issue
as well.
So have this is a basic rule of thumb at any given point of time do not have more than ten thousand
records owned by a single parent to a court order on it.
So these are some of the best practices that you can implement in data management.