I'm going on an extended holiday soon. (NZL :-D)
It's so happens that I had to restore this week.
Combining the 2 previous sentences, I came up with a question.
Who will do restores (If needed) when I'm away?
Turns out none of my colleagues knew how. So, "How to" documentation time! All is well again, until the question :
But how will that affect the replication?
After a bit of research, I couldn't give a proper answer.
As far as i'm concerned you don't overwrite DBs when restoring. Rename and/or recreate the publications via "Generate Scripts...".Therefore you shouldn't need to take any extra steps. But according to MS then you should restore the system databases at the time you restore your user DB.
This sounds a bit dodgey to me. What about all the changes to any other DBs or jobs changed created between the backup of the troublesome DB and the point it needs to be restored to?
One DB per instance? Doesn't sound very handy.
So what am I not getting here. I have never had to do File restores so don't know how this fits in.
Never restore using REPLACE? When testing this, it worked ok on a subscriber. Replication kicked in again after updating a published table.
Restoring a publisher with REPLACE, KEPP_REPLICATION did not go so smoothly. Had to recreate the replication.
Does anyone ever restore a DB with overwrite? Or does this just earn you a spanking?
Now i'm not sure if our backup strategy is sufficient.
Your wisdom and experience in this would be much appreciated.
(Sorry about the long post, got a bit carried away....:-P)
For better, quicker answers on T-SQL questions, read Jeff Moden's suggestions.
"Million-to-one chances crop up nine times out of ten." ― Terry Pratchett, Mort