Does this Application Server entitlement play into a decision into whether
or not to store PHP stuff in DB2 vs MySql (or whatever it's internal
engine is called)?
Granted, the main concern is your business and all. But people have
offloaded EDI to other boxes in the past because of exorbitant pricing
based on CPU, and other examples. If you're using your PHP to run a
website this pricing may be a tilting factor to the "let's keep it
separate in case we want to DMZ it or something" and we'll just replicate
the data from MySQL on the PHP lpar to DB2 on the production lpar??
Just wondering if this factors into the equation.
This thread ...
IBM i licensing: DB2 IBM i vs non DB2 IBM i (aka "Application Server entitlement"), (continued)
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact