SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: t2 who wrote (13600)12/29/1998 1:06:00 PM
From: rudedog  Read Replies (1) | Respond to of 74651
 
Tech -
good comments.
1. Why is IBM having a hard time outside of traditional IBM customers given DB2 is a great product?
My sense is that non-IBM customers question IBM's long term commitment to non-IBM platforms, rather than the services issue.

2. How long do you think it would take MSFT to move from 1/10 of the average number of users?.
This is more an issue of the reliability and scalability of the database. SQL 7 can handle thousands of clients, there is no technical reason why larger systems could not be built, but large customers still question the overall reliability of the product. Also, the simple fact that MSFT sells the DB in large numbers for very small (5 user or so) installations means that the average will be lower - it takes a lot of big installations to move the average numbers up given the installed base.

3. Could the demise of OS2 been partly due to the fact that IBM was in the PC business. That is, why would, for example, Compaq pick a competitor's OS, if one is available from MSFT (which does not manufacture computers) ?
There is way more OS/2 installed on CPQ than on IBM. There is more DB2 for NT installed on CPQ than on IBM. When the IBM DB2 team does demonstrations, they use CPQ hardware, because performance and clustering are better on CPQ than on IBM. This is only logical given CPQ's huge lead over IBM in the server space. The IBM server team is working to change this in regard to DB2.