Hi folks
We're looking to split an Intralink database in two: one chunk containing 10,000+ files (latest rev) in a couple of major folders, the other chunk containing 225,000+ files (the remainder of the Ilink 3.4 M060 DB).
Question is: anyone have an idea for a quick way to do it?
Based on a previous (much smaller) server split, I've been testing this scenario, but it's pretty time-consuming, even using scripts...:
1 - Export Dump file from starting database
2 - Create test server on another machine and import dump file
3 - Use SQL to switch all the filevault references (so as not to affect production data)
4 - Remove files we don't need (using a UI script, but takes AGES!)
5 - Resulting database can be dumped and exported to new location
Any advice or suggestions welcome: I'm thinking there may be a way to go further with SQL and hack off all the files we don't need... but it could be tricky. At present, people are still working on the production data, so we'll pick a time when we stop work and finally run the export/import to produce the off-shoot...
Ideally, we want to maintain file histories, hence not simply exporting latest revs.
Thanks in advance,
Edwin Muirhead
CAD Manager, Weatherford
