Skew Kepemilikan, Induk, dan Lookup

🌐 Juga tersedia dalam 19 bahasa

English · Español · 日本語 · Português (Brasil) · Français · Deutsch · Italiano · 한국어 · 简体中文 · Português (Portugal) · 繁體中文 · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)

Gambar dibuat dengan AI

Diterjemahkan dengan AI. Belum ditinjau oleh komunitas. Baca dalam bahasa Inggris Bagian ini telah berubah dalam bahasa Inggris dan belum diterjemahkan ulang. (35)

Modul 2 dari 4 dalam bab Merancang untuk Skala, bab 7 kursus Data Architect. Setiap modul dapat dibaca secara mandiri. Sebelumnya: Ketika Volume Mengubah Segalanya · Berikutnya: Ketika Volume Bertemu Model Berbagi

Pertanyaan yang dijawab modul ini: Apa yang terjadi ketika terlalu banyak rekaman menunjuk ke satu hal?

Masalah volume data besar tidak selalu soal terlalu banyak rekaman. Kadang soal terlalu banyak rekaman yang terhubung ke hal yang sama: satu pemilik, satu akun, satu induk, satu nilai lookup. Pikirkan lalu lintas. Sebuah kota bisa punya jutaan mobil dan tetap berjalan. Masalah dimulai ketika semua orang mengambil pintu keluar tol yang sama pada pukul lima sore. Totalnya penting, begitu pula konsentrasinya. Saya menyebut konsentrasi ini titik panas; Salesforce menyebutnya data skew. Ada beberapa jenis, dengan satu gagasan di baliknya: terlalu banyak aktivitas yang berkumpul di satu titik dalam model.

Skew Induk-Anak

The easiest to picture. One account with 100 contacts: nothing unusual. A thousand: probably fine. Ten thousand: now I’m paying attention. My design rule is no more than about 10,000 children under one parent, and Salesforce’s guidance draws the same line: “a large number of child records (10,000 or more) with a single parent account” is a common cause of poor performance (Parent-Child Data Skew (terbuka di tab baru)). Salesforce’s own example shows why. Put 300,000 contacts under one account. A user who can see one of those contacts gets implicit access to the account. When that user loses access to the contact, Salesforce has to check the other 299,999 contacts before it can decide whether to remove the user’s access to the account. Do that for many users at once, and it gets expensive. Salesforce also names one way to take part of that cost away: where your security requirements allow, set the child object to Controlled by Parent, so there are no parent implicit shares to maintain (same source). In practice, it’s the most common skew I see, and I’ve seen users notice visible lag at around 20,000 children under one parent. Where somebody feels it depends on what the system is doing. That’s why 10,000 is a design threshold, not a promise that record 10,001 breaks anything. The real question is: why are all these records pointing at the same parent? ⟲

Klik untuk memperbesar

Step 1 of 2: every line points at one account. That’s the hot spot. ⟲

Akun “Unassigned” dan Pool Akun

The classic case is contacts with no real account. Somebody decides every contact needs an account, so they create Unassigned Contacts and put every contact without an account there. Problem solved, until there are 300,000 contacts under it. We created an artificial hot spot because the model required us to put everything somewhere, and the relationship doesn’t even carry business meaning. It worked beautifully at 500 records. Then the Number of Zeros caught up with it. ⟲

What do you do when you’ve got a million contacts under it? I’ve seen child accounts by state, one unhandled-contacts account per state. I’ve seen an automatic version: whenever an account reaches 10,000, create another one. It can be a little awkward, but it spreads the load. ⟲

One answer is an account pool: Unassigned Contacts 001, 002, 003 and so on, with the children spread across them, each kept under the threshold. It works, and it’s Salesforce’s own advice: “Distribute child records so that no parent has more than 10,000 child records,” and for contacts without real accounts, “set up several dummy accounts and distribute the contacts among them” (Best Practices for Deployments with Large Data Volumes: General (terbuka di tab baru), Winter ‘27). But those aren’t real accounts; they’re architecture artifacts. Users will ask who “Unassigned Contacts 017” is and why it’s in their search results. So when I use a pool, I hide the placeholder parents from normal business experiences as much as I can. It’s a recurring trade-off: sometimes scale forces a structure that exists for the platform, not the business. When it does, don’t pretend it’s business data. Name it, document it, hide it where appropriate. ⟲

Klik untuk memperbesar

Step 2 of 2: the same contacts, spread across a pool. Nothing moved but where they point. ⟲

Master-Detail at Volume

Contacts under an account are a lookup. Master-detail is a different decision, and it’s one you make in the data model, long before the records arrive. Here’s the question I ask in class: would an invoice ever have more than 10,000 line items? No, it never would. So an invoice and its lines can be master-detail all day long. Now ask the same question of every master-detail relationship you’re about to build: at the volume we expect, will one parent ever pass 10,000 children? ⟲

Salesforce draws the same line: “As a best practice, don’t exceed 10,000 child records for a master-detail relationship” (Considerations for Object Relationships (terbuka di tab baru)). Master-detail is the strongest relationship Salesforce gives you, and that’s exactly why the number matters. The detail record has no owner of its own; its access is controlled by the parent. Delete the parent, and every child goes with it. A child can’t move to another parent unless you allowed reparenting. Roll-up summaries on the parent have to keep up as the children change. And saving a child can lock the parent, which is why Salesforce’s loading advice is to group child records by their parent “to minimize locking conflicts” (Loading Data from the API (terbuka di tab baru)). With ten children, none of that is noticeable. With a hundred thousand, every one of them is. ⟲

It’s also hard to undo. A master-detail relationship can only be converted to a lookup when the parent has no roll-up summary fields, and converting it changes the child’s sharing to Public Read/Write (same source). By the time volume tells you it was the wrong choice, the relationship may be holding up reports, sharing and automation. Count the children before you choose the relationship. ⟲

Steve Trucking has one of these decisions in its model. Each Retail Partner sends a Manifest (Manifest__c, a custom object) for each distribution center, for each working day. Manifest is custom, so master-detail to the partner’s account is allowed, and it’s tempting: the manifest would inherit the partner’s sharing, which is exactly the isolation we want. Now count. Our largest partner has nine or more DCs: nine manifests a working day, about 2,700 a year. Past 10,000 in under four years, under one parent, and every manifest revised on the day, so every revision would touch the partner’s account. That’s why the model makes Manifest a lookup and handles partner access through sharing. The invoice stays small; the manifests keep coming. ⟲

Klik untuk memperbesar

Step 1 of 2: master-detail, where the parent stays small. ⟲

Klik untuk memperbesar

Step 2 of 2: a lookup, where the children keep coming. ⟲

Watch Account with its contacts and opportunities too. It isn’t master-detail, but it behaves like a pseudo master-detail, with implicit sharing to the parent, which is why the 10,000 guidance shows up there as well. None of this means never use master-detail at scale. It means don’t choose a strongly coupled relationship and then act surprised that the records are strongly coupled. ⟲

Test knowledge. Know the 10,000-children guidance for master-detail, and what master-detail brings with it at volume: no owner on the detail (access controlled by the parent), cascade delete, no reparenting unless allowed, roll-up summaries, and parent locking when children are saved. Converting to a lookup needs no roll-up summaries on the master. ⟲

Skew Kepemilikan

Now the owner. I ask the room: who owns a million records? The admin? Is the admin sitting there creating a million records? Usually it’s the integration user or the data load user. The records come in, and nobody knows who to give them to. We create an integration user, it creates records, nobody thinks about ownership (“it’s just the integration user”), and a year later that user owns 2 million records. Salesforce calls it ownership data skew when one user owns more than 10,000 records of an object, and the classic example is all the unassigned leads parked on a dummy user (Ownership Data Skew (terbuka di tab baru)). That doesn’t mean a user can never own more. It means understanding the consequences: ownership isn’t a Created By stamp. It drives the role hierarchy, sharing rules and recalculation: behind the scenes, Salesforce keeps share records for the owner’s records above them in the role hierarchy. Attach millions of records to one owner who sits deep in the sharing model, and changing anything about that owner gets expensive. ⟲

The guidance matches what I teach in class. If a few users must own a very large number of records, give them no role; if they need one, put them in a separate role at the top of the hierarchy and don’t move them, and keep them out of public groups used as sources for sharing rules (same source). One catch with the top role: that user inherits access to all the data owned by or shared with the users below them. You could spread the records across a bunch of users instead, but for an integration user or a data load user, that typically isn’t worth the trouble. ⟲

We’re isolating the hot spot from the structures that trigger recalculation. Imagine a user who owns 5 million records being moved in a reorganization. That isn’t moving a box on the org chart; Salesforce may have to re-evaluate access across 5 million records. At this scale, organizational changes become data operations. ⟲

Test knowledge. Know the skew thresholds and the fixes: ownership skew when one user owns more than 10,000 records of an object (no role, or a separate role at the top that doesn’t move, and out of public groups used by sharing rules); parent-child skew at about 10,000 children under one parent. ⟲

Siapa Pemilik Rekaman Buatan Mesin?

Siapa yang membuat sebuah rekaman dan siapa yang memilikinya bukan pertanyaan yang sama. Redrock mengirim 500.000 pengiriman lewat API, dan pengguna integrasi yang membuatnya. Haruskah ia memilikinya selamanya? Mungkin, tetapi bukan hanya karena ia yang membuatnya. Dan sekarang agen juga membuat rekaman.

Posisi saya: bergantung pada apakah kepemilikan penting untuk berbagi. Pengguna integrasi atau agen adalah pengguna yang sah dan boleh memiliki rekaman. Jika kepemilikan menggerakkan akses di objek itu (lewat hierarki peran atau aturan berbagi), tetapkan rekaman ke pemilik yang dibutuhkan bisnis: pengguna sungguhan, antrean jika objeknya mendukung, atau pengguna pemilik khusus. Jika kepemilikan tidak menggerakkan akses, mempertahankan agen atau pengguna integrasi sebagai pemilik mungkin pilihan yang lebih baik, karena jejak auditnya langsung mengarah ke apa pun yang membuat rekaman itu. Bagaimanapun juga, putuskan apa arti Pemilik untuk objek ini, alih-alih secara mekanis menugaskan ulang setiap rekaman buatan mesin karena biasanya manusialah yang memiliki rekaman. Dan ingat bahwa Dibuat Oleh tetap ada: menugaskan ulang kepemilikan tidak menghilangkan fakta bahwa integrasilah yang membuatnya. Dibuat Oleh dan Pemilik menjawab pertanyaan yang berbeda. Membuat satu bidang menjawab keduanya adalah cara Anda mendapatkan model yang buruk.

Skew Lookup

A lookup can be a hot spot too: millions of records pointing at the same location, category, reference record or configuration record. Salesforce’s own training defines it: “Lookup skew happens when a very large number of records are associated with a single record in the lookup object” (Large Data Volumes: Design Your Data Model (terbuka di tab baru)). The danger isn’t “lots of lookups.” It’s concentration combined with activity: if millions of active records reference one record, and transactions keep touching that relationship, operations start colliding over it. That’s record locking, which chapter 11 covers. For now, recognize the shape: many active records, one heavily referenced record, worth inspecting. ⟲

Tidak Setiap Skew Sama Berbahayanya

Jangan menghafal “10.000 = buruk”. Lima puluh ribu rekaman historis yang menunjuk ke nilai referensi yang tidak pernah berubah, tanpa peran dalam berbagi dan nyaris tanpa aktivitas bersamaan, mungkin baik-baik saja. Dua puluh ribu rekaman aktif di bawah induk yang sering berubah, menggerakkan berbagi, mengisi roll-up, dan diakses beberapa integrasi sekaligus adalah cerita yang sangat berbeda. Volume punya bentuk, begitu pula skew. Berapa banyak rekaman yang berkumpul di sana? Seberapa sering mereka berubah? Apakah induknya berubah? Apakah hubungan itu menggerakkan berbagi atau penguncian? Apakah integrasi memperbarui anak-anaknya secara bersamaan? Apakah memindahkan pemilik atau induk memicu penghitungan ulang? Angkanya memberi tahu saya ke mana harus melihat; perilakunya memberi tahu seberapa khawatir saya harus.

Steve Trucking: Di Mana Titik Panasnya?

Dalam lima tahun kita memproyeksikan sekitar 9 juta perintah kerja. Misalkan seseorang berkata, “Biarkan pengguna integrasi memiliki setiap pengiriman.” Sembilan juta rekaman, satu pemilik. Apakah kepemilikan penting untuk berbagi pengiriman? Jika tidak, pemilik khusus bervolume tinggi bisa berjalan, diisolasi dari hierarki peran dan grup aturan berbagi seperti di atas. Jika penting, satu pemilik integrasi adalah model bisnis yang salah: integrasi membuat rekamannya; itu tidak berarti ia harus memilikinya.

Then the Retail Partner. Every work order carries its partner, deliberately, because partner isolation matters. But if one partner is 40% of the business, five years of deliveries is about 3.6 million work orders under one partner account. Does that make the relationship wrong? No. The business relationship is real, and I’m not going to invent 400 fake Redrock accounts because I don’t like the count. But I am going to look for a split the business would recognize. Each partner has real distribution centers, so a child account per DC under the partner spreads the work orders nine or more ways while every account still means something. Add archiving completed deliveries after the claims window, and the active children per parent stay low. ⟲

Itulah perbedaan antara kedua perbaikan. “Unassigned Contacts” sejak awal sudah buatan, jadi memecahnya menjadi pool tidak menghilangkan makna apa pun. Redrock adalah mitra sungguhan; memecahnya menjadi Redrock 001, 002, dan 003 akan merusak model. Memecahnya menurut DC-nya yang nyata tidak merusak. Perbaikan skala tetap harus menjaga makna. Kadang jawabannya adalah hubungan, strategi berbagi, pola kueri, model penyimpanan, atau kebijakan arsip yang berbeda, tetapi tidak pernah identitas palsu untuk entitas bisnis yang nyata.

Klik untuk memperbesar

Inspect, not bad. Concentration matters, not the total. ⟲

Temukan Titik Panas di Diagram

Ini latihan yang saya sukai. Ambil model datanya dan lihat panah-panahnya, bukan hanya objeknya. Untuk setiap hubungan, tanyakan: berapa banyak rekaman yang bisa menumpuk di sisi panah ini? Lalu tanyakan hal yang sama tentang Pemilik. Sekarang bayangkan tiga tahun, lima, sepuluh. Di mana rekaman berkumpul? Sering kali di situlah masalah esok hari bersembunyi.

Di luar ujian: apa yang diubah AI. Seseorang mungkin membuat 20 rekaman sehari; sebuah agen bisa membuat ribuan. Beri agen penggunanya sendiri, biarkan setiap rekaman tetap dimilikinya, dan skew kepemilikan muncul jauh lebih cepat daripada yang pernah terjadi dengan manusia. Kepemilikan oleh agen tidak salah, tetapi putuskan apa arti Pemilik untuk rekaman buatan agen sebelum volumenya menjadikan pilihan bawaan bagian dari arsitektur.

Yang Diputuskan Arsitek di Sini

• Di mana hubungan induk-anak, kepemilikan, atau lookup memusatkan rekaman, dan apakah cukup aktif untuk menjadi titik panas.
• Apakah rekaman buatan mesin tetap dimiliki integrasi atau pengguna agen, atau ditugaskan ulang karena kepemilikan menggerakkan akses.
• Bagaimana pemilik bervolume tinggi diisolasi dari hierarki peran dan grup aturan berbagi.
• Kapan induk buatan bisa dijadikan pool, dan kapan hubungan nyata justru butuh pemisahan yang bermakna.
• Whether each master-detail relationship stays under about 10,000 children per parent at projected volume, or should be a lookup. ⟲

Satu juta rekaman yang tersebar di ribuan pemilik dan induk berperilaku sangat berbeda dari satu juta rekaman yang menunjuk ke satu tempat. Cari titik panasnya sejak dini: pemilik, induk, lookup, di mana pun Jumlah Nol berkumpul. Tujuannya bukan menghapus setiap hubungan besar; sebagian mewakili bisnis dengan benar. Tujuannya mengetahui ke mana lalu lintas mengalir sebelum Anda membuka jalan tolnya, karena begitu jutaan rekaman menuju pintu keluar yang sama, mengubah jalannya jauh lebih sulit.

Jelajahi

• Salesforce Developers, Best Practices for Deployments with Large Data Volumes, Loading Data from the API (terbuka di tab baru) (Winter ‘27): group child records by parent to minimize locking conflicts, checked 2026-11-01. ⟲
• Salesforce Help, Considerations for Object Relationships (terbuka di tab baru): no more than 10,000 child records for a master-detail relationship; converting master-detail to lookup, checked 2026-11-01. ⟲
• Salesforce Developers, Designing Record Access for Enterprise Scale (Winter ‘27): Ownership Data Skew (terbuka di tab baru) and Parent-Child Data Skew (terbuka di tab baru), checked 2026-11-01. ⟲
• Salesforce Developers, Best Practices for Deployments with Large Data Volumes: General (terbuka di tab baru) (Winter ‘27), the 10,000-record owner and parent guidance, checked 2026-11-01. ⟲
• Trailhead, Large Data Volumes: Design Your Data Model (terbuka di tab baru): parent-child, ownership and lookup skew, checked 2026-11-01. ⟲
• Salesforce engineering blog, Managing Lookup Skew to Avoid Record Lock Exceptions (terbuka di tab baru) (2013; older, but still the clearest explanation; checked 2026-11-01). ⟲
• SteveTechArc, Salesforce Documents by Release: these guides, once a year from Winter ‘16, each with an archived copy. ⟲