Finance | Project Operations, Human Resources, ...

Problem with growing database transaction log file

(1) Share

Report

Posted on by Shooowtek

845

Hello,

A few days ago, I upgraded the local developer version of oneBox to version 10.0.39. Now I am currently having problems updating the database. These problems have never occurred before.
The problem is that I am already running a database synchronization after the database has been properly imported. The synchronization takes a very long time. I got to the point that for some reason some transaction (probably in a loop) inserts a log, resulting in an increase in the size of the database transaction log file. the file already occupies more than 100gb and eventually the synchronization fails when the disk runs out of space.

I tried with changing the recovery Model of the database to Simple from Full and with disabling the automatic growth of the log file.

Does anyone have any suggestions?

Sync freezes with below messages:

Log level - Warning | [DbSync: 7.0.30647.0] [Platform: 7.0.7198.66] [SourcePlatform: 7.0.7198.66]: WideIndexesValidator: Table 'RETAILTRANSACTIONSALESTRANS' has index 'IX_RETAILTRANSACTIONSALESTRANS_TRANSACTIONID' with a high number of columns: 48
Log level - Warning | Table 'PDSCOMDPRICINGTEMPLATE' in the DB does not yet contain any indexes.
Log level - Warning | Table 'PDSCOMDPRICINGMARGIN' in the DB does not yet contain any indexes.
Log level - Warning | Table 'PDSDISPOSITIONMASTER' in the DB does not yet contain any indexes.
Log level - Warning | Table 'INVENTINVENTORYDATASERVICEWHSQUEUE' in the DB does not yet contain any indexes.
Log level - Warning | Table 'INVENTINVENTORYDATASERVICEWHSQUEUEBACKUP' in the DB does not yet contain any indexes.
Log level - Warning | Table 'PDSCOSTBASIS' in the DB does not yet contain any indexes.
Log level - Warning | Table 'INVENTINVENTORYDATASERVICEONHANDADJUSTMENTQUEUE' in the DB does not yet contain any indexes.
Log level - Warning | Index 'TransactionNumberIdx' on table 'AdvancedLedgerEntryHeader' cannot contain field 'TransactionNumber' which is disabled, field will be removed from the index
Log level - Warning | Unique Index 'TransactionNumberIdx' will not be created on Table 'AdvancedLedgerEntryHeader' because the field: 'TransactionNumber' is disabled and removed from the index.
Log level - Warning | Index 'VoucherAccountingDateTranNumIdx' on table 'AdvancedLedgerEntryHeader' cannot contain field 'TransactionNumber' which is disabled, field will be removed from the index
Log level - Warning | Index 'StagingIdx' on table 'AdvancedLedgerEntryStaging' cannot contain field 'HeaderTransactionNumber' which is disabled, field will be removed from the index
Log level - Warning | Unique Index 'StagingIdx' will not be created on Table 'AdvancedLedgerEntryStaging' because the field: 'HeaderTransactionNumber' is disabled and removed from the index.
Log level - Warning | Primary Key on Table 'AdvancedLedgerEntryStaging' is set to disabled index: 'StagingIdx'. The index will not be created.
Log level - Warning | Index 'StatusOrigStartDateTimeIdx' on table 'BatchJob' cannot contain field 'recurrenceData' of type container, field will be removed from the index
Log level - Warning | Index 'EngChgEngineeringBomIdx' on table 'BOM' cannot contain field 'EngChgEngineeringBOM' which is disabled, field will be removed from the index
Log level - Warning | Index 'EngChgEngineeringBomIdx' will not be created on Table 'BOM' because index does not have any fields defined on it.

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Kevin Xia Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

It is important to set up a cleanup schedule to ensure that database logs are cleaned regularly to mitigate the performance impact. You can refer to this official document: Configure database logging - Finance & Operations | Dynamics 365 | Microsoft Learn. It introduces about database logging and performance, how to Clean up database logs.

Best regards,

Kevin

Was this reply helpful? Yes No
Martin Dráb 240,281 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Switching to the Simple recovery mode is a good idea; you should have done that at the beginning. Then you'll likely want to shrink the transaction log. Verify the size of the log and the amount of the available space after that.

Disabling auto-growth is dangerous. If a bigger log file is needed but it can't grow, the database server will stop working even if there is enough disk space available.

It's still possible, though, that some process wants to create an enormous transaction (consuming all available space).

The warnings mentioned above don't seem related to your problem.

Was this reply helpful? Yes No
Shooowtek 845 on at

Like (0)

Report
Copy link

Link copied!

Hello Martin,

I switched to simple recovery mode. The database transaction log file was about 2GB at the time. I started synchronization and unfortunately the file keeps growing..

Is there any way I can check what is causing this? Do you have any ideas on this?
I have no idea how to solve this problem quickly. The database I imported is from the LCS test environment.

Thank you.

Was this reply helpful? Yes No
Martin Dráb 240,281 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Yes, the transaction log grows when a process (such as the DB sync) is running and transactions aren't committed yet. That's the expected behavior.

Make sure you have a reasonable amount of disk space available.

You can reduce the size of the transaction log to zero, if you want. But having 2 GB as the starting size is fine too.

Was this reply helpful? Yes No
André Arnaud de Cal... 306,672 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi Shooowtek,

Did you run a full database backup after switching to the simple recovery mode?

Was this reply helpful? Yes No
Shooowtek 845 on at

Like (0)

Report
Copy link

Link copied!

Hello Andre,

Increasing the disc space solved the problem.

Thanks.

Was this reply helpful? Yes No