I had a database on a drive that failed. It got corrupted, but only 3 tables. It was moved to a new drive. Then due to choices that were not mine to make, it was decided not to restore from an untainted backup and to instead rebuild these three tables. I did this and everything looked good. It passed DBCC Checkdb after that and all functions that called those tables began working again without error. So far so good.
My question is that after all's said and done, I've got this persistent file that I've never seen before. It's "databasename.mdf_MSSQL_DBCC15" and I can't delete it because it's in use. I thought it would delete when I ran another successful DBCC Checkdb but the file doesn't seem to be going anywhere.
Is this file important? Can I just stop MS SQL Server Service and then delete it? What are the best practices for this? Why did it get created at all? I've tried to google for DBCC15 file type and there seems to be a shortage of information available to the general public of the internet (or my search criteria were exceptionally bad, I suppose).
- This topic was modified 6 months, 3 weeks ago by Mary K.