Replica size growth

121
3
12-07-2022 06:36 AM
JoeHershman
MVP Regular Contributor

Hi,

There may be a better place to post this, but not sure where

We have an app that has been in the field for a while (few years).  What we are seeing is unexplained growth in the replicas which does not match the amount of data being added.  There are replicas growing to almost a GB in size, but if we regenerated the replica (so has the same number of records) it is about 1/3 that size.

Would love to understand why this occurs, and looking from a solution that could compress these down so we do not have to push new replicas (this is deployed to close to 1000 devices)

Thanks - joe

0 Kudos
3 Replies
MichaelBranscomb
Esri Frequent Contributor

Hi Joe,

Do you mean the replicas themselves have been in the field on devices for a few years and are growing incrementally after synchronizing?

 

Thanks

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

@joe A couple of options to consider:

  • On the replica mobile geodatabase itself, you can try running the SQLite vacuum command (e.g. via a SQLite .NET NuGet package or via a SQLite database browser tool)  
  • On the Enterprise geodatabase side you could try running the Trim Archive History GP tool.

 

0 Kudos
JoeHershman
MVP Regular Contributor

Sorry slow replying

  • Yes this is for replicas that have been deployed since the original deployment, so a couple years+ and have just been growing over time
  • I was looking at the sqllite vaccum command and just need to find some better info on exactly how to run on the db, but not as part of a update or insert statement
    • The easiest thing would be if we could setup something that could run on a periodic basis, maybe at app startup.  Pushing an updated application is the simplest process in place
0 Kudos