DEV Environment H:\MSSQL_LOGS Disk Full, Cannot Import New Database

(0) Share

Report

Posted on by HAIRUL HAZRI

1,214

Hi,

I'm restoring UAT database to DEV environment, but failed to import. Error message was something like:

The source contains users that rely on an external authentication provider that is not supported by the target. These users will be treated as users without logins.
The transaction log for database 'AxDB_Sept2020' is full due to 'ACTIVE_TRANSACTION'

I figured this is most likely because the MSSQL_LOGS disk is full

Inside the Disk, there are still Logs for already deleted databases, but we cannot delete without administrator privilege.

How can we clear some space so that we can import a new database successfully?

Thank you.

I have the same question (0)

All responses (6)

Answers (2)

HAIRUL HAZRI 1,214 on at

Like (0)

Report

Wait a minute, UAT environment is Version 10.0.12 (10.0.507.10035),

while DEV environment is Version 10.0.12 (10.0.507.20028).

Are they not compatible? The only difference is quality update, so it should be fine, am I right?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report

Well, importing a database from a system that has a newer D365 version is not expected to work. Sure it can work sometimes.

Anyway your disk space has nothing to do with versions.

If it's a cloud hosted VM in your own Azure subscription you can increase disk sizes.

If it's MS managed environment (as it seems to be in your cas), you can't change the disk sizes. But you can create a service request and ask Microsoft to delete files from the system (just tell them what you want them to delete).

Another option is to try to clean up unneeded data (log/history tables) in the source UAT system before exporting the database.

Was this reply helpful? Yes No
Suggested answer

Luke Sha on at

Like (0)

Report

For 1st issue, I assume you export database from UAT manually without perform preparation script. Please export database by LCS service operation. It will make sure all the Azure SQL container users are removed

For 2nd issue, please submit support case. We will try to remove unused files or reallocate disk.

Was this reply helpful? Yes No
Verified answer

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

For the first issue, it's just a warning. It will still import the database without issues.

For the database disk space, you can try shrinking the transaction logs. Please check here for the steps.

Another alternative would be to back up your database and move it to LCS. You can stop the services and delete the existing AxDB database and then proceed with the import

Was this reply helpful? Yes No
Verified answer

vinitgoyal2005 6,332 on at

Like (0)

Report

Hi,

Follow steps mentioned here for import-export: docs.microsoft.com/.../dbmovement-scenario-exportuat

To clear the log you can use the Shrink DB option from SSMS and clear the logs: www.mssqltips.com/.../

You may have to change the database recovery model from FULL to SIMPLE

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Thank you everyone. Shrinking the log files got me to free up around 10GB, enough to import the db. Cheers.

Was this reply helpful? Yes No