All,
I'll start with the fact that I am not the "SQL Guy" or a SQL DBA. I'm working on a new client's backups and found that they have a Windows Server 2008 R2 server running SQL Server 2008 R2 Standard that hosts a SharePoint DB. This server stopped
backing up a few days ago and it appears the server is out of available overhead for VSS to complete snapshots.
Additionally, the SQL DBs hosted on this server appear to not have been backed up since mid 2015. This is due to the SharePoint DB's LDF being ~214 GB. The MDF itself is only 650MB and it appears their original SQL maintenance plan had not been configured
correctly to complete the log truncation.
After discussions with the client, they do not require point in time recovery but do have some concerns with a switch to Simple Recovery. As I'm not versed in SQL, I'm looking for some input. Below is what we're trying to gauge.
1.) How long would SQL take to flip the DB from Full to Simple Recovery Model with such a large LDF? (The client is a 24/7 shop and requires a high level of uptime and strict outage windows).
2.) Once the Full to Simple Recovery operation has been initialized, can it be stopped without any detrimental effects to the production DB? (They pose this question in the event the process time is determined to be excessive) My gut says it would be similar
to terminating a CHKDSK operation on a NTFS volume, you never stop it once it's started, unless you want to risk data loss or corruption.
Below are the full specifics for the server and SQL:
===========================
Server: Windows Server 2008 R2
SQL: SQL Server 2008 R2 Standard RTM (10.50.1600.1)
Database: 650MB MDF / 214GB LDF
============================
Any and all help is greatly appreciated and thank you for your time.