Add layer to an existing replica.

[BrentHoskisson]

Is there any way to edit a replica set to add a new layer to it?

Brent

[JoeBorgione]

Not sure what you are asking, but when you replicate data, as I understand it you are acutally replicating the database.  You don't have to replicate all the feature classes in a database but if you replicate one, you can certainly replicate more.

[EricVenden · Accepted solution]

Brent,
Try one of these:

http://support.esri.com/en/knowledgebase/techarticles/detail/35679

http://resources.esri.com/help/9.3/arcgisengine/dotnet/da79f58c-971a-454e-bc52-974c2c47e26a.htm

I realize that last link is for 9.3, but it should work for 10
Hope this helps.
Eric V

Is there any way to edit a replica set to add a new layer to it?

Brent

[HeatherMcCracken]

Brent,
Try one of these:

http://support.esri.com/en/knowledgebase/techarticles/detail/35679

http://resources.esri.com/help/9.3/arcgisengine/dotnet/da79f58c-971a-454e-bc52-974c2c47e26a.htm

I realize that last link is for 9.3, but it should work for 10
Hope this helps.
Eric V

These are the right links to be looking at.  Remember that you will need to add the new replica dataset to both the replica geodatabases (parent and child).  For example, you can use the code to add it to both sides, or you can use the code to add it to one side, and then use the schema synchronization tools to add it to the relative replica. 

-Heather

[Kevin_MacLeod]

12 years later, same question.  Links broke.  Sure would be nice if this was possible. In fact it would be nice if there was a simple way of replicating an entire SDE to a file GDB.  (All feature classes, all domains, all versions) That way never any need to fix replicas. Of course, each version would be its own fGDB. But a one-click solution would be great. I'm sure the official answer is "Python". (Or ArcObjects)  For now I'll just build a bunch of replicas and periodically have to rebuild them them and update them when schemas change and we add layers. This is also frustrating since then it breaks scheduled Synchronize runs.  Seems like this would be so simple to implement and save almost every enterprise customer time.