web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Trying to get CRM tabl...
Customer experience | Sales, Customer Insights,...
Answered

Trying to get CRM table size under control : LocalizedLabel ?

(2) ShareShare
ReportReport
Posted on by Victor 365 67
Dear community,
I'm managing two CRM environements (one UAT and one PROD) for years.
All our table size are growing but remains under control let's say, you know the DB cost is very expensive.
One though, the "localized label" table, is by far the largest (see below) and we have "only" 8 languages managed in there.
I'm questionning the size of this table, but Microsoft will only answer "delete languages" if you want to gain free space.
I mean it's 8 languages, and we have hundreds of thousands of records (if not millions) in other tables like Activities, Accounts, Contacts, and those tables are 1/4 the size of the LocalizedLabels.
As we did different migrations in the past (from premise to cloud for example), I wonder if we don't store old and useless data.
Have you faced the same question ? Is there a way to optimize this table ?
thank you !
 
Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Victor 365 Profile Picture
    Victor 365 67 on at
    Trying to get CRM table size under control : LocalizedLabel ?
    Thanks for your replies, I will tackle this and let you know if we have a positive outcome.
    We indeed have a lot of customization and solutions, that could explain the size...
  • Vahid Ghafarpour Profile Picture
    Vahid Ghafarpour 11,940 Super User 2025 Season 2 on at
    Trying to get CRM table size under control : LocalizedLabel ?
    If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

    To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

    Thanks for being an active part of the Dynamics 365 Community! 😊
  • Verified answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,833 Super User 2025 Season 2 on at
    Trying to get CRM table size under control : LocalizedLabel ?
    Hello Victor 365,
     

    You've hit on a common and often frustrating issue with Dynamics 365 (now Dataverse): the "LocalizedLabel" table growing excessively large, even with a seemingly reasonable number of languages. This table stores all the localized text for labels, messages, and other UI elements, and its size can become problematic.

    Let's break down the issue and explore potential solutions beyond Microsoft's standard "delete languages" response.

    Understanding the Problem:

    • LocalizedLabel Table: This table stores localized strings used throughout your Dynamics 365 environment.

    • Growth Drivers:

      • Number of Languages: While 8 languages isn't excessive, it still contributes to the table's size.
      • Customizations: Every custom entity, field, form, view, and message you create (and localize) adds records to this table.
      • Solutions: Importing managed or unmanaged solutions, especially those with many localized components, can significantly inflate the table.
      • Migrations: As you've suspected, migrations can bring over unnecessary or outdated localized data.
      • System Updates: In some cases, system updates might introduce redundant localized data. 

    • Microsoft's Response: As you've noted, Microsoft's default response is often to reduce the number of languages. While this might free up space, it's not always a practical solution.

      •  

    Potential Solutions and Optimization Strategies:

    1. Identify and Remove Unused Localized Components:

      • Solution Analysis:

        • Carefully review all imported solutions.
        • Identify any solutions that are no longer used or have been superseded.
        • If possible, delete these solutions. 

      • Customization Audit:

        • Conduct a thorough audit of your custom entities, fields, forms, views, and messages.
        • Identify any components that are no longer needed or have been deprecated.
        • Remove these components and their associated localized labels. 

      • Tooling:

        • Use the XrmToolBox plugin "Solution Analyzer" to help identify unused components. 

    2. Clean Up Deprecated Languages (If Applicable):

      • If you've previously supported languages that are no longer needed, remove them.
      • Caution: Ensure you have a backup before deleting languages. 

    3. Investigate Language Packs:

      • Verify that you're only using the necessary language packs.
      • Remove any language packs that aren't required. 

    4. Review System Jobs and Background Processes:

      • Some system jobs or background processes might be generating excessive localized data.
      • Review your system jobs and disable or optimize any that are problematic. 

    5. Dataverse Search Indexing (Less Likely):

      • In some cases, Dataverse search indexing might contribute to the LocalizedLabel table's size.
      • Investigate your search configuration and consider optimizing it. 

    6. Advanced SQL Queries (Use with Caution):

      • Warning: Use extreme caution when running SQL queries directly against your Dataverse database. Incorrect queries can damage your environment.

      • Identify Redundant Data:

        • You might be able to identify redundant or duplicate localized labels using SQL queries.
        • For example, you could look for labels with identical text but different language codes. 

      • Cleanup Script (Expert Level):

        • If you're comfortable with SQL, you might be able to create a script to remove redundant or outdated localized data.
        • Important: Thoroughly test any SQL scripts in a non-production environment before running them in production.
        • This is not officially supported by Microsoft and can cause issues. 
         

    7. Contact Microsoft Support (Escalate):

       

      • If you've exhausted all other options, escalate your support ticket with Microsoft.
      • Emphasize the disproportionate size of the LocalizedLabel table compared to other tables.
      • Request a more in-depth analysis of your environment.
      • Ask for specific guidance on optimizing the table.


        •  

    Important Considerations:

    • Backups: Always back up your Dataverse environment before making any changes.
    • Testing: Thoroughly test any solutions in a non-production environment.
    • Microsoft Support: Consult with Microsoft Support before attempting any advanced SQL queries or cleanup scripts.
    • Long-Term Management: Implement a strategy for regularly auditing and managing your localized data.

      •  

    By following these strategies, you can potentially reduce the size of your LocalizedLabel table and improve the performance of your Dynamics 365 environment. Remember to proceed with caution and consult with Microsoft Support when necessary.

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak
  • Suggested answer
    Saif Ali Sabri Profile Picture
    Saif Ali Sabri 2,346 Super User 2025 Season 2 on at
    Trying to get CRM table size under control : LocalizedLabel ?

    Optimizing the LocalizedLabel Table in Dynamics 365

    The LocalizedLabel table in Dynamics 365 can grow excessively large, especially in multi-language environments, and Microsoft’s standard response is to uninstall unused language packs. However, given your situation—only 8 languages and a disproportionate table size compared to other critical entities—there may be historical or redundant data inflating its size. Below are several strategies to optimize this table without removing necessary languages.

    1. Analyze the Content of LocalizedLabel Table
    Before taking action, analyze what is consuming space in this table:

    • Use Advanced Find or FetchXML Queries to check the number of records per entity.
    • Identify entities generating excessive labels. Custom entities and old configurations may contribute significantly.
    • Look for unused fields that still generate labels across multiple languages.

    🔹 Query Example: Count the number of records per entity in the LocalizedLabel table:

    sql
    SELECT ObjectId, COUNT(*) as LabelCount
    FROM LocalizedLabel
    GROUP BY ObjectId
    ORDER BY LabelCount DESC
     

    This will help determine if certain entities are over-consuming space.

    2. Identify & Remove Unused Metadata
    Localized labels are created for every entity, field, view, form, and option set in every language. If historical metadata remains after migrations, it could be causing excessive growth.
    ✅ Steps to clean up unused metadata:
    1. Review Unused Custom Entities & Fields:
      • Navigate to Settings → Customizations → Customize the System
      • Identify old or deprecated entities and attributes
      • Delete or deactivate unnecessary custom fields
    2. Check Unused Option Sets & Forms:
      • If old option sets exist from past migrations, they might contribute unnecessary localized labels.
      • Delete unused forms & option sets from Power Apps Maker Portal.
    3. Verify & Remove Redundant Labels from Migrations
    If you've migrated from on-premise to cloud, redundant localized labels may have been carried over.
    • Compare the number of active fields and forms with the number of localized labels.
    • If old translations exist but are no longer needed, consider re-importing translations with only the necessary labels.
    ✅ Steps:
    1. Export translations:
      • Go to Settings → Customizations → Export Translations
      • Open the XML file and look for unnecessary labels
    2. Remove redundant labels and re-import the cleaned file.
    4. Reduce the Number of Managed Solutions Installed
    Each managed solution can bring its own localized labels, even if you don’t use them.
    • Identify unnecessary managed solutions under Settings → Solutions
    • Remove unused or legacy solutions that add unnecessary labels.
    5. Verify if Labels are Indexed or Stored Inefficiently
    Sometimes, SQL indexing inefficiencies can bloat tables.
    • Use Dataverse Storage Capacity Reports to check whether LocalizedLabel is contributing to query slowness.
    • If you find performance issues, raising a Microsoft Support Ticket may be necessary.
    Conclusion
    Instead of simply deleting languages, a structured cleanup approach will help optimize the LocalizedLabel table:
    ✅ Analyze what is consuming space (query table sizes)
    ✅ Remove unused metadata & translations
    ✅ Clean up historical migration leftovers
    ✅ Uninstall redundant managed solutions
    ✅ Optimize indexing & Dataverse queries if necessary.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 258

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 180

#3
Tom_Gioielli Profile Picture

Tom_Gioielli 92 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans