Baker, Given the scenario you have just outlined, and my imaginings of the way that each of the 3 systems SHOULD work, you have no likelihood of deadlock collisions (this could be guaranteed with possibly relatively minor "tweaks" to all sides of the equation).
If you want a "solution", I just need a few more FACTS (guestimates AOK for numbers) - what is the database behind the WCS system - does the WCS have automated/robotic picking, manual/RF or a combination - average number of line items on a transaction originating from the Universe system - average line items for an order from the web portal - assume you want LIVE inventory on the portal (may be reasons why this is BAD, but that is another story) - peak transactions/hr from OLTP & web portal Baker, I know you mean well, but I'm just questioning the need for "Fastest" in this scenario, unless I see some seriously LARGE numbers for some of the above :-) Ross Ferris Stamina Software Visage > Better by Design! [ad] BTW, we also do applications, covering areas like web ordering, warehousing, distribution etc .... just for the record, and have had to tackle issues like this before [/ad] >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Baker Hughes >Sent: Thursday, 25 October 2007 12:20 AM >To: [email protected] >Subject: RE: [U2] Fastest Bi-Directional data transfer btwn MV and non- >MV dbms > >Ross, > >Yes, there is a real-world application to the question, at least one >where I may try to 'sell' the solution after the theory is worked out. >3 Different systems play with the same live Inventory of products: a >UniVerse based OLTP, a MS SQL db based web-order portal, and a Warehouse >Control System which fills the orders and receives stock. At night we >batch the daily stock receipts from WCS up to UniVerse, update the Avail >to Sell qty for the OLTP and allocate Order Reserve Qty to backorders. >Then UV sends the updated ATS to the web database (which is always 24 >hours behind). > >Ross has asked the most astute question in all this, that of data >collisions, where the same product is updated on 2 or 3 sides at once. >This is perhaps the question that looms largest and keeps people (like >us) in batch mode rather than real-time. > > >Thanks everyone for the very worthy contributions to this science. >-Baker > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Ross Ferris >Sent: Wednesday, October 24, 2007 1:58 AM >To: [email protected] >Subject: RE: [U2] Fastest Bi-Directional data transfer btwn MV and non >MV dbms > >Baker, > >How "live" and "active" is this bi-directional transfer likely to be? Do >you need to consider the possibility of data collisions (ie: will >someone change a record in your UV database that could also be changed >on the "other" end) .... OR are the discrete changes somewhat "atomic >transactions", with no chance of duplication > >Are both systems running "live" databases? What are you REALLY trying to >do (your question is nearly as big as Texas) ... if you have some >specific goal in mind, then some potential road blocks may be removed >(or emerge) > >Ross Ferris >Stamina Software >Visage > Better by Design! >------- >u2-users mailing list >[email protected] >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
