Remove dependence among feature classes participating in a topolgy when replicating

JohnFell — Wed, 05 Oct 2022 23:14:24 GMT

I asked the question "Is it possible to exclude feature classes from replication that participate in a topology on the parent?"

After reading the web help I found that...

"All feature classes participating in a topology are replicated together. Individual topology feature classes cannot be excluded from a replica." See help topic.

In this case where editors have a geometric network or parcel fabric with over a million features in a production -> publication environment replication would produce significant overhead in the publication workspace due to unnecessary data being replicated.

A workflow providing for topology in the production environment and more flexibility for replicating only the desired feature classes and features based on a sql query would prove helpful.

Re: Remove dependence among feature classes participating in a topolgy when replicating

AllanBenvin — Thu, 20 Sep 2012 15:59:37 GMT

We have the same situation. We only want to publish some of our data not everything.
We also want to be able to re-organize the data in the published GDB. We do not necessarily want it to be in the same feature datasets that it was in the source GDB.

idea Remove dependence among feature classes participating in a topolgy when replicating in Data Management Ideas

Remove dependence among feature classes participating in a topolgy when replicating

Re: Remove dependence among feature classes participating in a topolgy when replicating