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.
Strategies & Market Trends : Gorilla and King Portfolio Candidates
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: emmeling who wrote (15050)1/13/2000 1:59:00 PM
From: Rickus123  Read Replies (2) of 54805
 
Tracey,

I agree with you when you say:

When Oracle standardized on IBM's SQL language, that did not make their architecture non-proprietary -- it simply gave it an open interface.

My interpretation of the RFM was that the authors seemed to think that the standardization on SQL was a key to achieving gorilla power.

I would argue that the gorilla-ness didn't come until the client/server tornado, when the need for a performance enhancement like row-level locking became more critical, and Oracle's solution seemed to be the one that was adopted.

The query example helps illustrate my point. That query (in my experience) would run the same on DB2, Informix, SQL Server, as well as Oracle (and presumably any other SQL implementation)

But since the client/server tornado changed the landscape in that there were suddenly multiple users accessing/updating the same data concurrently, the standard (SQL) was not enough.

I can tell you that from a database programmer's point-of-view, it is no simple task to move an application from one database platform to another. Very high switching costs.

Bingo. I have had precisely the same experiences. But the switching costs, in my opinion, have more to do with the non-SQL aspects of the RDBMS implementation than with SQL itself.

The more I think about it, this case study is an excellent example of the difference between committee-based and proprietary architectures. (I guess that's why it was a case study.<g>)

Thanks for your response.

--Rick
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News