Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Suspected recovery model interference between DEV and PROD db's (same name)


Suspected recovery model interference between DEV and PROD db's (same name)

Author
Message
jjturner
jjturner
Old Hand
Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)

Group: General Forum Members
Points: 343 Visits: 513
Eirikur Eiriksson (8/25/2014)
jjturner (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?
Cool

5 people
Eirikur Eiriksson
Eirikur Eiriksson
SSCertifiable
SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)

Group: General Forum Members
Points: 6812 Visits: 17756
jjturner (8/25/2014)
Eirikur Eiriksson (8/25/2014)
jjturner (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?
Cool

5 people


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..."
Cool

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.
jjturner
jjturner
Old Hand
Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)Old Hand (343 reputation)

Group: General Forum Members
Points: 343 Visits: 513
Eirikur Eiriksson (8/25/2014)
jjturner (8/25/2014)
Eirikur Eiriksson (8/25/2014)
jjturner (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?
Cool

5 people


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..."
Cool

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.

Cheers Cool
John
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search