Latest Contributions by PasiHyvonen

‎01-16-2015

The solution we ended up using was to setup separate one-way parent to child replicas from the remote sde geodatabase into file geodatabase in the central office. So each one has its own parent, or target, FGDB. We then have a python script that combines the data from all those replica fgdbs into a central sde geodatabase. That python that combines data isn't changes only, it simply reloads the data in sde from those fgdbs.Takes few hours to run but that is ok as a nightly task. Advantage of that is it is very simple (the simplest possible replication scenario) and in case anything goes wrong with one replica we can just re-create that without affecting others.

‎11-09-2009

I can't really see what is new here in 9.4. This technical article: http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=34200 describes how you can setup one way child to parent replicas and it was already there for 9.0. What does 9.4 add to this? I was hoping the new thing in 9.4 would be that there is no need to copy all data into the parent first. It is the moving of data with globalIDs that I would like to avoid. We have a set of 'orphan' child geodatabases without a parent. I would like a parent GDB simply to 'adopt' these child GDBs and accept data from them. The initial sync, or setting up the replication, would get all existing data from the child GDB tables and feature class into the parent. Pasi

‎11-04-2009

Could someone confirm how the new one-way child to parent replication in 9.4 will work? (I haven't got 9.4 geodatabases setup yet for testing...) Currently (pre 9.4) one-way child to parent replication works only for one child. Trying to register another child replica to same parent fails with error saying target already contains data. Workaround is to get copy of the all the child GDBs data to parent and then create replicas with 'register with existing data' option. Problem with that is copying data without changing globalIDs... Will 9.4 make all this easier and simply allow me to create one-way replicas from multiple child GDBs to one parent GDB, without the hassle of copying data first? Scenario I have is where 30 district geodatabases all maintain their own data (same schema, just data for different area). What I need is up-to-date copy of all districts data in the head office GDB for analysis and reporting. This new 9.4 one-way child to parent replication sounds like it could be the solution... Thanks, Pasi

Online Status	Offline
Date Last Visited	‎02-09-2024 03:18 PM

My Ideas

Latest Contributions by PasiHyvonen

Re: Is there a non-ArcObjects option?

Child to parent replication

Child to parent replication

Child to parent replication

Esri Forestry Group (EFG)