We have a team working on OPM piping specs and currently have roughly 30+ files (of size 1.2GB), this might go up to 45+ pipe specs(one .mdb file per spec) and might have more than 2GB size for these specs, is there a way to optimize/compress the size of .mdb files? Any recommendations?
Why are we looking for this data optimization?
We plan to use managed workspaces in a distributed environment and since catalogs/specs get loaded on user PCs through these managed workspaces, the download time could be a nightmare for the user.
Hello Parijat,
It's a bit strange why your .mdb files are so large. Usually a spec file size ranges from 1 MB to maybe 10-20 MB for a really large one. Please try opening the files in MS Access and in database tools use the Compact and Repair Database tool. That should decrease the size of the file drastically.
If this does not help, could you please then send us one of your larger spec files for a review what could be wrong with it.
Regards,
Justinas
Answer Verified By: Parijat Jamdar
Hi Justinas,
Apologies for the delay in reply to your post, I was on vacation. We figured out that some of the catalogs/specs were way too large and we can live without them. The Compact and Repair Database tool in MS Access didn’t help in compression. We are good for now. Another quick Q – Is it necessary to have all the out of the box OPM catalogs to be a part of managed workspace in PW? Can we still live with only selected catalog/specs that we have created? Is there any dependency of these catalogs with out of the box catalog/specs in OPM?