Skip to content

Commit 04d2d7a

Browse files
arihant-2310vjdhama
authored andcommitted
Spell checks fix
1 parent e9c4a5e commit 04d2d7a

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

content/blog/hive-to-unity-catalog-data-migration-databricks.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,7 @@ essential data.
5252

5353
We collaborated with multiple stakeholders, from schema owners to data engineers, for input on which tables were
5454
critical and required for daily operations. This information-gathering stage identified schemas for migration and
55-
non-essential
56-
ones for removal, enhancing the organization’s data efficiency.
55+
non-essential ones for removal, enhancing the organization's data efficiency.
5756

5857
## **Execution Phase**
5958

@@ -113,7 +112,7 @@ Successfully transferred **~22 TB** to Unity Catalog, with **~75 TB** of depreca
113112

114113
#### **Cost Savings:**
115114

116-
By removing 75 TB of deprecated data, we reduced both storage costs and data handling overheads. Heres a rough
115+
By removing 75 TB of deprecated data, we reduced both storage costs and data handling overheads. Here's a rough
117116
breakdown of cost savings:
118117

119118
| **Cost Type** | **Details** | **Annual Cost** |
@@ -129,11 +128,11 @@ read/write operations are not included in the above cost breakdown but contribut
129128
### **Enhanced Governance and Operational Efficiency**
130129

131130
- **Improved Data Governance:** Unity Catalog introduced clear data lineage and granular access control, essential for
132-
maintaining regulatory compliance. Unity Catalogs centralized governance model also provided the ability to enforce
131+
maintaining regulatory compliance. Unity Catalog's centralized governance model also provided the ability to enforce
133132
consistent access controls across environments, significantly improving both security and compliance management.
134133

135134
- **Operational Efficiency:** Before the migration, engineers spent significant time maintaining outdated or unnecessary
136-
jobs. Considering, ~10 unused jobs required about 1 hour per week to manage, removing those jobs saved approximately
135+
jobs. Considering ~10 unused jobs required about 1 hour per week to manage, removing those jobs saved approximately
137136
10 hours of engineering effort each week. This freed up valuable time for engineers to focus on core operational
138137
tasks, accelerating product delivery and reducing maintenance overheads.
139138

@@ -161,5 +160,5 @@ safeguarding production workloads and preventing any data loss. This careful app
161160
it was crucial for ensuring operational continuity and preserving data accuracy. The migration optimized the governance
162161
model, reduced costs, and enhanced operational focus.
163162

164-
Stay tuned for an upcoming series of blog posts where well dive deep into the technical processes and scripts used,
163+
Stay tuned for an upcoming series of blog posts where we'll dive deep into the technical processes and scripts used,
165164
including enabling Unity Catalog for an existing production Databricks setup. 🚀

0 commit comments

Comments
 (0)