Good day We are currently on IMODSE 9.2 and looking for the best approach to refreshing all our lower environments (dev and test) with a copy of our production database config. Won't get into why we want to do it, lets just say the lower environments got very stale... As I see it I have 2 options, but really not sure which approach is the best, least intrusive Utilize the Azure SQL database restore for restoring prod backup onto test and dev, or Utilize transporter With both approaches, I appreciate, I will need to make various environment specific config changes manually, like DB connection strings, sync project changes etc. Keen to hear if someone in the community has had to do something similar and which approach they followed, or can advise us to use? Thanks in advance DK

Best practice for restoring IMODSE database (lower environments)

daniell kilian_72010 4 months ago

Good day

We are currently on IMODSE 9.2 and looking for the best approach to refreshing all our lower environments (dev and test) with a copy of our production database config. Won't get into why we want to do it, lets just say the lower environments got very stale...

As I see it I have 2 options, but really not sure which approach is the best, least intrusive

Utilize the Azure SQL database restore for restoring prod backup onto test and dev, or
Utilize transporter

With both approaches, I appreciate, I will need to make various environment specific config changes manually, like DB connection strings, sync project changes etc.

Keen to hear if someone in the community has had to do something similar and which approach they followed, or can advise us to use?

Thanks in advance