I would agree with that, you could also skip database c and just overwrite database B and run the SQL statements to recreate/modify the objects that are different or dont exist from database A. only issue would be changes.... dont want to be revisiting this thing all the time.

I would look at what is different and determine if it actually needs to be in database B. You could do your restore to database B and in database C change whatever those things are to point to database B.

Example if you have sprocs that modify the data or views you use to read the data just keep that stuff in database C. Use database C as sort of an access point to get to database B. Then you can run your restore without the need to change anything in database B.

hth - tom