Difference between revisions of "Help:About/archive/2007 migration issues"
(clarification about plans) |
(→2007-11-08 updates: working on packages/shipments) |
||
Line 15: | Line 15: | ||
* '''09:59 Technical stuff''': I've moved the last two major tables over, and am now working on some minor tables. | * '''09:59 Technical stuff''': I've moved the last two major tables over, and am now working on some minor tables. | ||
* '''18:52 Some things working''': Found a way to make those tables unnecessary, yay! And rewrote the order import routine (which securely downloads orders from the web server) so it's working again, yay! Now I just have to see which other parts need fixing... | * '''18:52 Some things working''': Found a way to make those tables unnecessary, yay! And rewrote the order import routine (which securely downloads orders from the web server) so it's working again, yay! Now I just have to see which other parts need fixing... | ||
+ | * '''19:50 More things working''': The list of order items in stock now works, and I can bring up orders to package. Still working on the package-creation process, and management of shipments. |
Revision as of 00:51, 9 November 2007
- The problem - summary: I am in the process of reconfiguring the order management software so that most or all of the order data is stored on the web server instead of on a single machine. Problems with Microsoft Access's interface to the web server's database caused order processing to suddenly stop working towards the end of October. The problem is taking longer to fix than I had expected.
- What this means: I can't easily look up order information (without taking large chunks of time away from fixing the problem), and I can't process orders at all. The data is still there, but it takes forever to load and sometimes locks up the computer (a problem compounded by our lousy internet connection, because of which I am switching services -- the new service is scheduled to be installed Nov. 13).
- What I am doing about it: I've dropped every other technical project and am now spending every available hour working on the problem. Normally, a data migration is something which would be done by a team of IT people working 8-12 hours per day; I have myself, working maybe 4 hours on a good day (in between transporting kids and running errands). I have now migrated about 3/4 of the affected data, and I have a plan which I hope will allow order processing to start working again once the data is all copied over.
I apologize to all the customers whose orders have been delayed, often past their requested deadlines; I will provide complete refunds (including shipping both directions) for any orders which need to be returned due to being late.
No data has been lost or compromised; this is purely a design/programming problem. As usual, no credit cards will be charged until orders are ready to ship, and orders may still be canceled at any time.
This is not a normal situation, and this is not how I like to do business. On the up-side, the data migration should allow me to add a lot of requested services, such as automatic email notification of shipments and online order management, when it is complete, but this is not how I had planned for the conversion process to go.
Again, my apologies to everyone affected by this.
-- Nick, 2007-11-07
2007-11-08 updates
- 09:59 Technical stuff: I've moved the last two major tables over, and am now working on some minor tables.
- 18:52 Some things working: Found a way to make those tables unnecessary, yay! And rewrote the order import routine (which securely downloads orders from the web server) so it's working again, yay! Now I just have to see which other parts need fixing...
- 19:50 More things working: The list of order items in stock now works, and I can bring up orders to package. Still working on the package-creation process, and management of shipments.