With database mirroring, if the mirror database fails, the transaction log space on the principal database cannot be reused even if we are taking transaction log backup. This mean we need to have enough space for the transaction log to grow or bring mirror database online before the logs fills up the availabale disk space or break the database mirroring.
If we lost our principal database, and we force to switch on the mirror database with the "SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS" command. After, the old mirror is now principal with the disconnected status because the old primary stil unavailable.
During this time and until the old principal become mirror and online, do I have a transaction log space pressure on the new principal ?