Home
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
UPS Subsidiaries
UPS Information Technology
Think, re-think, think ahead- OUT THINK
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="upscorpis" data-source="post: 306007" data-attributes="member: 2017"><p>The reason not to allow the customer owned DB to be the WS DB is to minimize support issues. It is generally good pratice to protect your operational data store and allow others to use copies of the data for their own purposes. This allows the owner to optimize things based on their needs and protects the operational store from corruption and/or contention. I agree that some customers would be capable of supporting their own DB. You are correct that a large portion of the WS footprint is DB. The problem goes back to the diverse customer base. Imagine allowing this type of thing to the masses. It would be a support nightmare. A more controlled approach might be successful. I'm not sure we're hearing a lot of customers asking for this feature given the accessibility of the data via the methods we've already discussed. I'm not against it per se - I'm just not sure it's a slam dunk decision. A similar discussion would evolve for allowing direct SQL access to the DB.</p><p></p><p>Based on your comments, I think the new AJAX air freight may be a little different than you might be envisioning. The GUI actually loads on the client on first use so after the first load, the delay is minimized and it becomes very snappy. There are remote calls for processing shipments so those will tend to be slower. If you know about the freight business process, a remote call is required to create a pickup request. There is no way around this.</p><p></p><p>I agree with your point that freight wasn't deployed optimally the first time in WS. It wasn't gold plated out of the gate. Things will improve in that arena as time passes and we get feedback from customers and folks like yourself.</p><p></p><p>BTW, I don't mean to pee in your corn flakes so I hope you're not taking it that way. I love discussing this stuff with folks that deal with it daily. Good discussions are a great way to get the synapses firing correctly.</p></blockquote><p></p>
[QUOTE="upscorpis, post: 306007, member: 2017"] The reason not to allow the customer owned DB to be the WS DB is to minimize support issues. It is generally good pratice to protect your operational data store and allow others to use copies of the data for their own purposes. This allows the owner to optimize things based on their needs and protects the operational store from corruption and/or contention. I agree that some customers would be capable of supporting their own DB. You are correct that a large portion of the WS footprint is DB. The problem goes back to the diverse customer base. Imagine allowing this type of thing to the masses. It would be a support nightmare. A more controlled approach might be successful. I'm not sure we're hearing a lot of customers asking for this feature given the accessibility of the data via the methods we've already discussed. I'm not against it per se - I'm just not sure it's a slam dunk decision. A similar discussion would evolve for allowing direct SQL access to the DB. Based on your comments, I think the new AJAX air freight may be a little different than you might be envisioning. The GUI actually loads on the client on first use so after the first load, the delay is minimized and it becomes very snappy. There are remote calls for processing shipments so those will tend to be slower. If you know about the freight business process, a remote call is required to create a pickup request. There is no way around this. I agree with your point that freight wasn't deployed optimally the first time in WS. It wasn't gold plated out of the gate. Things will improve in that arena as time passes and we get feedback from customers and folks like yourself. BTW, I don't mean to pee in your corn flakes so I hope you're not taking it that way. I love discussing this stuff with folks that deal with it daily. Good discussions are a great way to get the synapses firing correctly. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
UPS Subsidiaries
UPS Information Technology
Think, re-think, think ahead- OUT THINK
Top