I don’t know if it’s doable or not, but I made an idea for a Data only refresh option to move data from one database to another. See the ticket for more details and to vote.
1 Like
It’s a cool idea but I am skeptical that it would be practical. If you are restoring a whole db you can’t pick and choose which tables get restored - its just the whole db. And if you want to load data table by table that is so much code.
If it were easy, I would just do it myself… It may be a pipe dream, but we’ll see what they say.
1 Like
How do you imagine this working?
Optional table exclusions maybe?
Their maybe a bigger idea lurking inside this one.
I’m not sure. I’m just hoping that it’s separated enough to be able to do something.
Likewise, I fully agree with and support this idea, since I have no concept of what limitations exist to stop it.
I mean, the gist of what I am reading here is, “Make it much faster for me to refresh a test database with fresh data to play with - but don’t mess with the BPMs, BAQs, or Functions, or Apps that I am developing.”
Amen to that.
[Edit - and I see you spelled that out already in the Idea. Anyhoo, I voted for it.]
2 Likes
I’d be happy with the ability to transfer a single table from one DB to another. For example, uploading (DMT) 100k+ record to a UD table in PILOT to work on customizations. It would be great, when ready, to just transfer that UD table to LIVE instead of having to re-DMT all those records.
I think this would be good, but it would be complicated. There are some inherent GUID linkages that might need to be recreated during a data-only transfer, but it could be done I suppose. And then there is the problem of version/patch levels needing to be the same - or maybe not depending on any schema/data changes to the tables being copied.
Mostly, we on-prem folks keep a Pilot/Test database set up for our users to try things that they’ve never done before, or for basic patch testing - and moving some fresh data over is very helpful with certain transactions - in particular, open jobs/orders so we can finish the quote to cash cycle without having to recreate everything from scratch. But the same goes with Purchasing/AP and AR/GL data - testing those cycles need a lot of test data.
We also keep a Dev/Sandbox environment in order to do development and major upgrade testing before it goes to the Test/Pilot environment for UAT, so being able to move some fresh data to that environment would help us too - especially since any development work in process would get eliminated by a full DB copy. We export things now and reimport them, but it would be nice to just move over some fresh data.
Here’s another one (I’m full of ideas today). We do have to add indexes and is one of the things that I wouldn’t want to have to have the cloud team do due to the amount if testing it takes to see if/when things work. If there was a self service way to do it in the UI, that would be awesome. You can already see them in the data dictionary, and the script to make new indexes isn’t hard to generate.
2 Likes