I have reason to believe the transaction log file on my database is corrupt.
This database is involved in transaction based replication (both subscription and publishing), and I'm unable to start its log reader agent with an error message which cites "Operating System Error 23".
I essentially just want to do what it takes to be able to restart the log reader agent, and my best idea so far is to somehow clear the log file, detach from it and reattach to a new log file. I'm not sure what the data loss implications of this would be though. Is this the best solution or is there a better way to deal with a corrupt log file? It is not a production database so avoiding data loss is not absolutely necessary (though preferable). There are no backups.