Here's the original email text for the kill_bcd deployment, plus more helpful instructions...
Instructions
The install program's readme file *should* give the user instructions. From experience, this utility doesn't seem to have much impact on the Heritage Programs (as their data sets are not as large as they were for the Central BCD). Nevertheless, if the BCD has known unresolved issues with its indexing system, it may be wiser to use KILL_BCD so that those issues will not compromise the export.
Original email text... It sounds like a joke, but it isn't. If you want the XML dump to run just as fast as you can get it to run, this might help. Please do not broadcast email this out to people--I give it to you as a last-minute "ticket" you hand over when they are about to run the final export from the snapshot BCD. Its effect will be the most profound on the EOR file. Attached is a little one-time utility to break a BCD (removes all indexes, all auditing, all that wonderful stuff that makes the BCD what it is--it's soul). At the same time, it makes file access faster (it sped up the Central BCD XML dump by 3 times). For those of you who want to tinker, the batch command is KILL_ALL_BCD_MFS and it must specify all the volumes explicitly (thus, you can limit the damage to just BCDDATA and not BCDSYS, or add other data volumes if you think you need to). At any rate, as a last step, carefully controlled, the NHP can install, then execute KILL_ALL_BCD_MFS to effectively break the BCD. It still has all its standard functionality (Marcos & Tyler are using a "broken BCD" now for their BCD-HDMS Data Exchanges), but it is not designed to make the BCD quite work the way you'd expect, only without indexes and auditing--in fact, it is a quick and dirty program and its effect is not totally known. Installation alone does not break the BCD. The user must execute KILL_ALL_BCD_MFS to break it. Back to ExportDataForConversion
|