Hi everyone,
We are using Acumatica SaaS and don’t have direct access to the production database.
We get a .bak file from the portal to restore a copy locally.
We can restore that .bak to our local SQL Server — that works fine. But we want to keep our local DB up to date without restoring the whole .bak each time.
Is there a best practice to replicate only new or updated data or only way is ODATA/API?
Please Guide
Thanks
Best answer by Dmitrii Naumov
In that case I think you are covered with the db backups or snapshots (that you can download from the Acumatica instance directly). Snapshots also allow you to select datasets you’d like to take from the production, e.g. f you only need the configuration, but not the actual transactions.
I’d assume you do not need the real-time replica of the data all the time, but rather want to update it once in a while.
+7
What is your goal here? What are you going to do with that database?
It’s quite an unusual request.
Thanks for asking — let me clarify our actual goal so it makes sense.
We are developing and testing customizations in our Acumatica environment. To properly test these custom features, we need realistic Production-like data, not just the standard demo/sample data that ships with Acumatica.
+7In that case I think you are covered with the db backups or snapshots (that you can download from the Acumatica instance directly). Snapshots also allow you to select datasets you’d like to take from the production, e.g. f you only need the configuration, but not the actual transactions.
I’d assume you do not need the real-time replica of the data all the time, but rather want to update it once in a while.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
