Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan contoh harga Data Catalog.
Pertimbangan harga Data Catalog
Biaya penyimpanan metadata untuk tag akan ditagih ke project tempat template tag dibuat.
Biaya API ditagih ke project yang berbeda-beda, bergantung pada panggilan tertentu:
Metode baca (get, lookup, list, dan search) ditagih ke
project akun yang memberikan otorisasi untuk panggilan API.
Metode tulis (create, update, delete, dan rename) untuk semua entity yang disimpan, kecuali tag, ditagih ke project entity yang diubah.
Metode tulis untuk tag ditagih ke project template tag yang digunakan untuk membuat tag.
Contoh harga Data Catalog
Tag kecil
Pengguna A membuat dan menerapkan tag kecil (masing-masing 1.024 byte).
Dengan biaya $10 per bulan, pengguna dapat menyimpan metadata sebesar 5 GiB, yang setara dengan
sekitar 5 juta tag. Dengan asumsi satu tag per tabel, totalnya ada
5 juta tabel yang diberi tag.
Pengguna B membuat 5 juta tag berukuran 1 KB pada tanggal 10 setiap bulan,
dan menghapus tag tersebut pada tanggal 20. Biayanya adalah $3,33, yang dihitung sebagai 5 GiB data dibagi dengan sepertiga bulan:
5GiB * $2 // 5M tags using 1K bytes memory each amounts to 5GiB of metadata
* 1/3 // The tags were stored for 10 days (between the 10th and 20th day of the month), so the cost is divided by one-third.
---
= $3.33
Tag besar
Pengguna C membuat dan menerapkan tag besar (masing-masing 10 ribu byte).
Dengan biaya $10 per bulan, pengguna dapat menyimpan metadata sebesar 5 GiB, yang setara dengan
sekitar 500 ribu tag. Dengan asumsi satu tag per tabel, jumlah totalnya adalah
500 ribu tabel bertag.
Pengguna D membuat 10 template (misalnya ETL, Tata Kelola Data, Kualitas Data), dan menerapkan tag besar (masing-masing 10 ribu byte) menggunakan setiap 10 template.
Dengan biaya $10 per bulan, pengguna dapat menyimpan metadata sebesar 5 GiB, yang setara dengan
sekitar 500 ribu tag. Dengan asumsi 10 tag per tabel, jumlahnya menjadi
50 ribu tabel bertag.
Memperkirakan harga silsilah data
Contoh harga urutan data
Pengguna E mengaktifkan silsilah data untuk melacak silsilah untuk
BigQuery dalam project mereka. Project berada di lokasi us-central1. Selama 1 bulan, urutan data menggunakan 100 DCU-jam pemrosesan Dataplex Premium, dan menghasilkan 1 GiB metadata urutan data. Biayanya sebesar:
100 * $0.089 // 100 DCU-hours of Dataplex Premium processing billed at $0.089 per DCU-hr
+ (1GiB - 1MiB) * $2 // cost of storing 1GiB data lineage metadata excluding 1MiB of free storage per month
---
= $10.9
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-02-01 UTC."],[[["\u003cp\u003eThis page provides details on Data Catalog pricing, including metadata storage and API call charges, along with specific cost examples.\u003c/p\u003e\n"],["\u003cp\u003eMetadata storage costs for tags are billed to the project where the tag template was created, and read method API calls are billed to the project of the account that authorized the call.\u003c/p\u003e\n"],["\u003cp\u003eThe cost of tag storage is calculated based on the size and quantity of tags, for example, $10 per month allows for storing 5GiB of metadata, which translates to approximately 5 million small tags (1024 bytes each) or 500,000 large tags (10K bytes each).\u003c/p\u003e\n"],["\u003cp\u003eData lineage pricing involves Dataplex Premium processing charges (billed per DCU-hour) and metadata storage costs (excluding 1MiB of free monthly storage).\u003c/p\u003e\n"],["\u003cp\u003eWrite method API calls for all stored entities except tags, are billed to the project of the mutated entity, whereas write method API calls for tags are billed to the project of the tag template used to create the tag.\u003c/p\u003e\n"]]],[],null,["# Data Catalog pricing examples\n\nThis page provides examples of Data Catalog pricing.\n\n### Data Catalog pricing considerations\n\nMetadata storage charges for a tag are billed to the project where the tag\ntemplate was created.\n\nAPI charges are billed to different projects depending on specific calls:\n\n- Read methods (`get`, `lookup`, `list`, and `search`) are billed to the project of the account that authorized the API calls.\n- Write methods (`create`, `update`, `delete`, and `rename`) for all stored entities, except tags, are billed to the project of the mutated entity.\n- Write methods for tags are billed to the project of the tag template used to create the tag.\n\n### Data Catalog pricing examples\n\n#### Small tags\n\n- User A creates and applies small tags (1024 bytes each). For $10 per month, the user can store 5GiB of metadata, which corresponds approximately to 5M tags. Assuming one tag per table, it amounts to a total of 5M tagged tables.\n- User B creates 5M tags of 1K bytes each on the 10th of the month,\n and deletes the tags on 20th. The cost is $3.33, calculated as 5GiB of data\n divided by one-third month:\n\n 5GiB * $2 // 5M tags using 1K bytes memory each amounts to 5GiB of metadata\n * 1/3 // The tags were stored for 10 days (between the 10th and 20th day of the month), so the cost is divided by one-third.\n ---\n = $3.33\n\n#### Large tags\n\n- User C creates and applies large tags (10K bytes each).\n For $10 per month, the user can store 5GiB of metadata, which corresponds to\n approximately 500K tags. Assuming one tag per table, it amounts to a total of\n 500K tagged tables.\n\n- User D creates 10 templates (for example ETL, Data Governance, Data Quality),\n and applies large tags (10K bytes each) using each of the 10 templates.\n For $10 per month, the user can store 5GiB of metadata, which corresponds\n approximately to 500K tags. Assuming 10 tags per table, it amounts to a total of\n 50K tagged tables.\n\nEstimate data lineage pricing\n-----------------------------\n\n| **Important:** Only certain executions generate lineage, which can differ between supported systems. For information on supported systems, see [About data lineage](/data-catalog/docs/concepts/about-data-lineage#lineage-supported-systems).\n\n### Data lineage pricing example\n\nUser E enables data lineage to track lineage for\nBigQuery in their project. The project is in the `us-central1`\nlocation. During 1 month, data lineage consumes 100 DCU-hours\nof Dataplex Universal Catalog Premium processing, and generates 1GiB\nof data lineage metadata. The cost is: \n\n 100 * $0.089 // 100 DCU-hours of Dataplex Universal Catalog Premium processing billed at $0.089 per DCU-hr\n + (1GiB - 1MiB) * $2 // cost of storing 1GiB data lineage metadata excluding 1MiB of free storage per month\n ---\n = $10.9"]]
