You can explore about the data synchronization service in ARAS (Theoretically knowledge but I didn't used the DSS yet)
Hi Gopi,
thanks for your post!
I once tried the DSS in another project. It killed the database and made it impossible to edit Parts.[emoticon:d3f592d49e434d7fb67e973881d4c367][emoticon:d3f592d49e434d7fb67e973881d4c367][emoticon:d3f592d49e434d7fb67e973881d4c367]
The current DSS version modifies a some of the default ItemTypes. So use it with caution. It´s a pretty complex project, I didn´t spend much time to understand how it works.
Regarding this topic I will probably use a mix of AML and SQL scripts. I will temporary copy the 2nd database to the main server. Then prepare the scripts for the data transfer and make a few test runs. When everything is fine, I make the cutover.
Basically a similar approach the Aras update team uses.
Scripts have the advantage, that I can include the required item modifications (link correct users identities, etc.). It requires a lot of preparation, but cutover can be reduced to minimum.
Nevertheless, I haven´t started yet. So I am still happy for any tips!
Angela
Angela,
I would like to hear how this goes for you. I am interested in this as well.
Nate
Basically this one is a test balloon for my own update concept.[emoticon:0e469978eb8947d18b9c41123db3725a]
When we one day get a new open release, I at least want to try to update. Of course this is easier said then done. With my current main database, I probably need 2 years of preparation (and cleanup) to cover everything.
But I made first tests and was able to transfer some Users+Alias from one db to another with SQL. It´s actually a pretty dumb concept.
