As another monk stated "It depends". There are many different factors that will determine how applicable the use of any product and how durable that product will be. Some questions you want to possibly ask are:
- Nature of the data being stored, that is does it contain data that for some reason product X (in our case DBI) does not handle well and requires a lot of massaging to work.
- What type of company are you in? Are you in the type that keeps detailed records of what is installed where and would know who to contact BEFORE it makes an upgrade or at a company that makes an upgrade and wonders why it can't access anything.
- Company policy. Does your company have a policy or commitment to its share holders or powers that be that it use only X type products? This may seem like it is an obvious thing, but I have been burned by it before. Make sure the solution you are suggesting is allowed on the network in the first place.
- Support Services. Who provides support for product X? Are they aware of it being implemented?
- Future needs. Is this company going to be able to manage product X in the future with its current mind set or is this something being brought in the back door in the dark of the night? Make sure the comany can and is willing to support product X, especailly if it is a critical app.
- Ability to justify. This is for when everyone has looked high and low for a solution that solves the problem, but some of the above items are missing. You need to present to them how product X can save them both time and money and illustrate how it can be applied to other areas.
