Skip to main content

#MSDyn365BC Reduce Data Stored in Business Central Tenant - Part 2?

Hi all,

In Last article we discussed about some quick ways to delete unused data from the system using standard Microsoft Batches.

I Hope you also feel in the same way as I do about cleaning up database to keep it manageable, easier to Upgrade and Upgradable to BC Online.

Clean Data also increases the performance of code. 

In this article, we will try to understand what else is in store for clean-up data in database.

Migrate BLOB data types to Media or MediaSet

Data in Media or Media set data types aren't counted in the database limit. As an extension developer, consider migrating data from blobs to the Media or MediaSet datatypes for your own extensions.

  • Data Stored in Blob is stored in Records and adds up to database size.
  • Data Stored in Media or MediaSet, is not stored in Records. Using Media and MediaSet, data is stored in system table 2000000184 Tenant Media or 2000000183 Tenant Media Set of the tenant database.
Each media object is assigned a unique identifier (ID) that act as a reference in the Source Record. Microsoft is already converting most of the Blob to Media Datatype. We as partners Developers Should Start doing same for our extensions.

Read More about Media and MediaSet in MSDN.



Use retention policies - 

Retention policies allow you to specify how frequently you want Business Central to automatically delete outdated data in tables that contain log entries and archived records.

With Retention Feature, Administrators can define retention policies to specify how frequently they want Business Central to delete outdated data in tables that contain log entries and archived records. 

Policies can include all data in the tables that is past the expiration date, or you can add filter criteria that will include only certain expired data in the policy.




In Next article in this series We will discuss about other possibilities that we have to keep our database size within permissible limit.

Stay connected.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.