Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : IFMX - Investment Discussion -- Ignore unavailable to you. Want to Upgrade?

To: bob gauthier who wrote (10628)	5/1/1998 3:15:00 PM
From: syborg	Read Replies (1) \| Respond to of 14631

ODBC the standard application protocol? ROFL.... thats a good one. Perhaps you have heard of Java or CORBA? I will give you some time to rethink that one. Of course using a multi-gig application on Wintel platform costing below $20K should give you plenty of time to think. The simple fact is that SQL Server does not scale! Period, end of story until possibly 7.0 and a decent operating system. Even if you put that aside, there are standards that perform better than ODBC. syborg

To: bob gauthier who wrote (10628)	5/1/1998 4:06:00 PM
From: Mark Finger	Respond to of 14631

>>Applications are increasing being written to ODBC standards making >>the choice of a DBMS platform a generic one. The lowest cost vendor >>wins (read SQL Server). We are implementing a significant >>application on a Wintel platform with considerable power, multiple >>gigabytes of storage, and a hardware cost below $20K. I know that for you this seems to be a large project, but by the current Gartner standard definitions, anything under 20G is considered SMALL. That is also why you can get by with ODBC interface. If you were really pushing the system, you would not be able to accept the cost of ODBC getting in the way. Remember that the whole MSFT answer is still vaporware. 1 1/2 years ago, 6.5 was going to solve everything for us. A year or so earlier, 6.0 was going to solve everything. So we are really to believe that 7.0 is now the answer. Further, 7.0 requires NT 5.0 with its moving date (it seems like the mirage, that is always a year away). Yes, MSFT can do high transaction rates on TPC/C, but it is limited by number of CPU's and complexity of queries. As for stability, just ask how many consultants have had good experience in 24x7 or 24x365 situations--most of the ones I know can only relate nightmares. In data warehousing, we just will have to wait and see. Certainly, the current version is inadequate. We simply have nothing else to go on for the future. In "object" technology, MSFT does not even have an acceptable road map in place, much less any thing in development. If they are as far behind as would appear, IFMX might really become entrenched before anything from MSFT is available.