Eirikur Eiriksson (8/25/2014) jjturner (8/25/2014) Eirikur Eiriksson (8/25/2014)
Yes, apologies for the tacit generalization (backup ~ backup/restore)
So further to the point, I'm having this DEV recovery model switch over to FULL a number of days after it got restored from PROD on Aug 6th - and as I tried to illustrate from the backupset, it was backing up as SIMPLE after the Aug 6th restore (because I manually switched it back to SIMPLE after the RESTORE), until it mysteriously switched to FULL recovery on Aug 14th...
Quick question, how many developers have the permission to do this?
Possibly that's 5 too many, you may want to use a friendly educational approach like "if you do this again I'll break your..."
On a more serious note, would there be a reason for any of these five to change the settings? Could it be a case of mistaken identity thinking it was the production environment (seen that happen)? Connection properties in Registered Servers within SSMS have an option of colour coding, good tool to prevent that kind of mistake.
I suppose I'll have to resign myself to accept that this was accidental human intervention and not some bizarre system-induced change. (Although that still doesn't explain why PROD backups are showing up in my DEV msdb backupset...)
My gut still tells me that swapping the database backwards and forwards between DEV and PROD has given my DEV instance a case of indigestion...
But thanks for the connection properties tip, I'll see if I can put that into effect.