We have a SQL Server 2017 Standard version where recently the CHECKDB is failing with the operating system error 665.
The fragmentation level of the disk drive is 0% as it is automatically defragmented weekly. The database is 24/7 OLTP database. Only way the checkdb completes is when we turn off the application. Now online solution suggests
- Increase the size of the disk drive, I have 800gb free space on the drive which has a database with 550 gb used space
- Defragment the data drive- Currently automatically defragment weekly
- Break the database into smaller files- Currently not possible due to downtime
- Consider placing the database files on ReFS volume which does not have the same ATTRIBUTE_LIST_ENTRY limits that NTFS presents. You must reformat the current NTFS volume using ReFS. – Again not possible due to downtime
Currently the checkdb checks with the option Physical only and using Ola Hallengreen script
My short term proposal is to do the checkdb into another server. But I am running out of ideas if there are other ways to cure the problem without any downtime.