sql server - Attaching a DB "inherits" schema changes from DB previously attached with same name -


we've experienced issue newly attached dev instance "picked up" schema changes had been made previous dev database not present in live db replica before renamed , attached dev.

the dev db starts log shipping standby restored, detached, files renamed , re-attached new dev db. note previous dev database not being deleted detached. note old , new dev dbs both "forks" of same original database.

now dev/test environment it's not particularly problematic makes me worry we'll create against silently changed dev break live when it's applied.

so working theory relates unique identifiers used sql server internals , possibly timing of changes dev.

can confirm or shed light on issue?

edit: further detail schema changes involved addition of new nullable columns @ end of few tables. admittedly minor , importantly did not involve actual data. also, log shipping copy in standby until reattached (so read only) , i've reviewed query logs verify no ddl changes run.

that said, unfortunately cannot replicate issue. not happen small db created test , deleted dev db , recreated full backup resolve issue cannot repeat exact process.

my goal in asking question ascertain whether we've experienced exceptional fluke or our process fundamentally unsound. i'm leaning toward exceptional fluke @ moment.


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -