This question already has an answer here:
My system has the main database as a principal (reads/writes only to that database) and then a mirror database on a different site that receives all database updates from the principal database.
This is all working fine, but the transaction log on the principal database is close to 80GB and growing. I have tried shrinking the log but that task fails every time. In my opinion I would not need the log at all, since all updates are mirrored to the other site.
Principal database needs to be in full recovery mode for the mirroring to work.
Can you give me some steps on how to get rid of that annoying transaction log or how to get it into a manageable size? Since the mirror site is my recovery method, can I just delete in?