Not thinking it through - Part 2
OK - First off, this isn't my routine I'm just an observer on the process running on a managed server!
Having had the index rebuild job fail due to insufficient transaction log space and query governor setting and the resultant code change leading to overwriting transaction logs which invalidated the recovery from the transaction logs, this weekend the job has finally been run successfully and the database indexes rebuilt. ( see Not thinking it through )
BUT ... to achieve this the database was set into simple recovery mode, the indexes rebuilt and the mode set back to full. The fatal flaw... no full backup after the job so the following transaction log backups will not be recoverable, and as the nights full backup failed due to a lack of disk space, once again a critical production database is being used for a working day with no recovery point. It's "school boy" or "school girl" errors but worrying from the point of view that this server is managed by an outsourced provider, and no I will not be naming names.