Destructive and Scripted Database Refresh


I’m often asked a question by customers on what we mean when saying we need a destructive refresh of the database or a scripted one for that matter. So here is a quick explanation.


A destructive refresh is basically make your environment be a copy of Another DB(Master, Prod, etc). In it I would take a backup of for example the Master DB and overwrite the DynamicsAX Trans DB.  Then I’d go in and change the pointers inside AX to point to your server instead of the Master server.


A scripted refresh keeps your pointers and some configurations, things like batch jobs and security, document handling and just copies most of the data from Master, going table by table.  Some tables are excluded in the scripted refresh, depending on what we are restoring.


Time taken: A destructive refresh will take about an hour to do, while a scripted refresh is 3-4 hours.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s