Below is a list of Frequently Asked Questions regarding local storage of images. For the purposes of this article, "XVCapture" refers to XrayVision DCV, Dentiray Capture, and all other rebrands.
Can my practice have a copy of all imaging data hosted locally?
Yes, but depending on the amount of data your capture program, XVCapture, may have degradation in performance as a result. Though the issue may not present itself immediately, it is certain to degrade over time and become worse as additional images are added. For this reason, we recommend not retaining a copy of your data locally.
Why is there a degradation in performance?
XVCapture’s local database (flat file type) is not designed to host a complete copy of all imaging data locally. It is designed to capture and store images temporarily until they are forwarded to the Apteryx cloud database.
What does the degradation look like?
Depending on the amount of data hosted, server performance, and number of images actively being queried/saved, during new image save, or existing image query you can expect up to a 30 second delay in addition to instability of the program (crashing/freezing).
What if I just want some historical data, not all?
Though this will not be an immediate issue, depending on the requested number of images stored, you can expect degradation to grow over time. XVCapture has no tools to manage and purge the local database based on capture date.
What is the recommended installation structure for XVCapture?
Apteryx recommends installing XVCapture per capture machine with purging enabled. This means that once the images are confirmed to have been received by Apteryx, they will be purged from local hard drive. This will enable your organization to capture even if your intranet, internet, or server are
completely down.