From: aka@ulysses.att.com (Atul Ashar) Subject: Re: ORACLE, MINI-SQL, INGRES Comparison Date: 1995/11/18 Message-ID: X-Original-Message-ID: #1/1 X-Deja-AN: 119645450 sender: netnews@ulysses.homer.att.com (Shankar Ishwar) references: <482700$t5i@carbon.cudenver.edu> organization: AT&T Bell Labs, Murray Hill, NJ, USA keywords: ORACLE MINI-SQL INGRES NULL STRUCTURE DISK SQL LOGICAL PHYSICAL newsgroups: comp.databases,comp.databases.oracle,comp.databases.ingres,comp.databases.theory In article <482700$t5i@carbon.cudenver.edu> ghharrac@ouray.cudenver.edu (George/Jorge) writes: >Hi, > >As a user of ORACLE, I am looking for information about what I consider >to be the major RDBMS and their usage of STRUCTURES ( ISAM, CISAM, HEAP, >HASH, ....) foreign concepts to ORACLE. How does the usage of these structures >affect the performance of the system ? I know what theory says, but I am >look from the users point of view. I also want information of the In case of Ingres, it works as per threory. With more choices of structures, we can really make good decisions wrt space/performance. However, I have one more point. In case of Oracle, primary key is also like secondary index in case of Ingres. i.e. Oracle does not structure table as per the primary key definition. This makes it flexible for altering primary key as it does not make rewriting of whole table again. >usage of ORACLE tablespace, to how Ingres and Mini-sql handle tables in >seperate files and their manipulation. What is better, the tablespace >concept of the 'others'? I can point out one difference (not a major one). You can move table from one location to other quickly as it is matter of moving file from one directory to other. > >George > >ghharrac@ouray.cudenver.edu >gharrach@carbon.cudenver.edu >