the file log filled the disk

I have been reviewing a database server that we have here and I see that Disk C, where the SQL Server is installed, is with 0 bytes available.

I have navigated through all the folders and I have noticed that the "Log" folder weighs 223 GB and inside that folder there are thousands of dump .mdmp files, I know that the dump files are generated when there is a problem in the server, so I started to find out on the internet and in a forum they mentioned that it could be that a database is corrupt, so I consulted the table sys.messages and found a suspicious error:

"An inconsistency was detected during an internal operation in database '%. * Ls' (ID:% d) on page% S_PGID. Please contact technical support." with the code 5242,

On the internet they mention that this error code indicates database corruption but in the message they do not detail what database it is.

So I started to run a DBCC CHECKDB to all databases and all are fine, the CHECKDB does not find any error

what should I do?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> An inconsistency was detected during an internal operation in database '%. * Ls' (ID:% d)

Ideally Database ID would be displayed instead of "% d". If not, then kindly check the databases present in the server to see which database it is..
R@f@r P@NC3RVirtualization SpecialistCommented:

Execute the following commands to validate the integrity of the database and its tables and please indicate the results, attachment reference link.

I remain attentive to your comments.

enrique_aeoAuthor Commented:
hi experts

What files can I delete to decrease the disk size?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

R@f@r P@NC3RVirtualization SpecialistCommented:

Frees the drive from the disk.
Defragment the disk.
Delete temporary files to recover space.

Share a printer to see the folders of the C drive

let me know the results.

I remain attentive to your comments.

enrique_aeoAuthor Commented:
Can I delete the dump files?
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Yes, you can copy few dump file alone and delete the remaining ones to free space on your log file folder.
Dump files are required for future storage if you are going to use Windebugger to analyze your dump files or involve Microsoft to analyze the dump files.
R@f@r P@NC3RVirtualization SpecialistCommented:

if you can delete them, generally the dump files are generated when the server has failures, but you can delete them without problems.

Vitor MontalvãoMSSQL Senior EngineerCommented:
I'm almost sure that you're databases are all in Full Recovery Mode and that you don't have any Transaction Log Backup job to truncate the log files.
Fast option is to change those databases to Simple Recovery Mode and then shrink their transaction log files so you can recover the disk space.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
enrique_aeoAuthor Commented:
The files . mdmp are being saved in the Log folder of Disk C where SQL Server C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log is installed, the .mdmp files are equal to the dump file I think, when you I right click on a dump file and see its properties, its extension is .mdmp

On the C disk the mdf and ldf files of the databases are not being saved, on the C disk there are only the installation folders and the 223 GB weight of the log referred to the Log of the installation folder C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log and it's just so heavy because every day a lot of Dump files are being generated

 On the other hand, we do not have visible problems with the bd server, everything works fine, it does not fall or anything, that's why I wanted to know why so many dump files are being generated daily or how could I identify what is happening to solve it? that eliminates the dump files and frees a little space, in a few days it is full again.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.