Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I'm afraid this workflow wouldn't really work (renaming and reattaching the vault) . The vault databases have information inside that uniquely identify them . So you would be blocked on the re-attach if there is already a vault attached with that unique identity.
Could you say what are your concerns regarding the database size?
Halve off the database is now legacy & only needs to be kept as a record - very unlikely to be used. Was thinking that reducing the database by 50% may improve the speed.
If accessing the files is pretty unlikely, have you thought about just storing a backup for archiving purposes and then deleting the stuff you don't need from the production system? If it turns out you need the files then it would just be a matter of restoring the backup onto a separate machine.
What kind of speed are you talking? We have a 50+ Gb database (over 1.2 million files) and we normally return a search in less than 10 seconds. We are still on VP2012 and that's still 32 bit. Should get better with VP2014.
The legacy would be nice to have, just in case.
Memory is cheap. Having to repetively bring a Vault back is time not well spent.
