Stu's Braindump

Hint: I tend to expect my conversion effort to run for about 24-36 hours all up (assuming the machine has been spec'ed to suit the customers implementation footprint and standard batch schedule expectations). This tends to include the migration to Prod, and Tidy Balances (including database backups at various stages throughout the process). As a rule of thumb though I tend to break the processing down to: ~10-20% - Input Transform (ie ConversionCentral) ~25-30% - Object Validation ~ 5-10% - Key Generation ~ 5-10% - Tidy Balances ~10-15% - Production Migration ~15-25% - Reporting

Question Received: A customer has asked me if its possible to keep the original account numbers when migrating information across to CC&B. My thoughts are that it could be done by inserting the account numbers into the key tables manually and not letting the migration create the account numbers. Whilst I think this is possible, I am going to steer the customer away from doing this because of the added risk to the migration process. I am however interested in your thoughts on this and if anyone has attempted it before? Answer: Whilst feasible to retain the old key values, it should be noted that the conversion effort would have to do a number of things to ensure that the old values are brought over: 1. All source keys must be unique numeric values. 2. Indentical values must be entered onto the CX_ID and CI_ID fields on tables traditionally populated by the KEYGEN conversion step (ie. all CK_* tables in the Staging Schema) (I recommend adding the same value to INIT_ID for co