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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

BYOD and entity size

(0) ShareShare
ReportReport
Posted on by 245

Is there guidelines on the amount of data that can be exported to BYOD before we need to consider Azure data lake?  We have some very large tables/entites (think Docuref, vendtrans, etc.) that have millions of rows, or multiple GB in size, we prefer to access all the data via TSQL so exporting to BYOD seems simplest/most logical for us.  However one of our D365 developers said initialization or re-initialization can be unreliable or costly in terms of time/hours and is not easy to troubleshoot if something goes wrong.  For example, if there is an issue with change tracking for, say, Docuref table or entity, and we had to reinitialize, it may take many hours.

As we are not in production yet, I cannot test/verify this, so I'm looking for guidance.

I have the same question (0)
  • Verified answer
    nunomaia Profile Picture
    25 Moderator on at

    I don't think there are any official guidelines on that topic. You should consider that many large tables ( ex: InventTrans ), if you enable change tracking and you open a performance ticket in Microsoft, you will get an answer that changing tracking in that table is not supported by Microsoft. Whenever possible use a datalake, for data extractions. For small databases, BYOD is simpler to manage and avoids many of the overhead that datalake has.       

  • pnwguy Profile Picture
    245 on at

    thank you nunomaia - is performance issue unsupported for large tables only, or does that include large entities as well?

  • nunomaia Profile Picture
    25 Moderator on at

    Is not on table size or entity number of fields, but on critical tables.

    I already got feedback from MS that "General Ledger Entries", "InventTrans", don't have support for incremental changes. It works, but we detected some SQL locking on those tables associated with change tracking

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 512 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 386

#3
Adis Profile Picture

Adis 259 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans