Hi @Avyayah ,
If DBCC CHECKTABLE reports any errors, then we recommend restoring the database from a database backup instead of using one of the REPAIR options to run REPAIR. If there is no backup, running REPAIR can also correct the reported errors. Depending on the database, you might be able to restore the database to a new name, then delete the problematic table and copy it from the restored version. This will depend on data dependencies, foreign keys, etc., and may also cause data loss.
If you run REPAIRde, I would recommend starting from the smallest risk to the largest risk. In other words, REPAIR_FAST first, if it doesn’t work, try REPAIR_REBUILD, if it doesn’t work, try REPAIR_ALLOW_DATA_LOSS. For more information, you can read carefully : DBCC CHECKDB (Transact-SQL).
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.