General Discussion

Data architecture is complex, to start with. Reconciling past versions to ensure compatibility and useful access is a major effort.

Polling and testing user expectations and adaptation is a lengthy, recursive process.

But more than all of those, the most difficult aspect of any major change in a database is getting everyone involved to understand what specifications will mean to them in terms of the finished product, and getting buy-in and participation from key players throughout the process.

If you can do all that and do it well, you might emerge with a usable, well-updated tool that will provide uninterrupted service and generate improved access and reporting of information.

Writing code for an entire massive hyperdatabase in one month?

If you believe that, I can sell you shares in some lovely waterfront real estate on great terms. PM me.

cynically,
Bright