home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!ames!network.ucsd.edu!sdcc12!oba!mstankus
- From: mstankus@oba.ucsd.edu (Mark Stankus)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: Database recommendations
- Message-ID: <37284@sdcc12.ucsd.edu>
- Date: 26 Aug 92 17:27:25 GMT
- References: <seaim=y00WA78imGZf@andrew.cmu.edu>
- Sender: news@sdcc12.ucsd.edu
- Organization: Mathematics @ UCSD
- Lines: 35
- Nntp-Posting-Host: oba.ucsd.edu
-
- In article <seaim=y00WA78imGZf@andrew.cmu.edu> da0g+@andrew.cmu.edu (David Apfelbaum) writes:
- >
- >It looks like I am going to need to tie together a rather large amount
- >of data as we convert an existing database's datafiles over to the NeXT.
- > DBKit seems to be an ideal solution. However, that still leaves a
- >choice of Sybase or Oracle for the underlying database.
- >
- >So, are there any recomendations? Advantages or Disadvantages?
- >
- >
- > Thanks for your time....
- >
- > -David Apfelbaum.
- > da0g+@andrew.cmu.edu
-
-
- Check out ParaBase -- it makes the database use easier
- and acts as a front end to Sybase or Oracle.
-
- Mark Stankus
-
-
-
-
-
-
-
-
-
-
-
-
- --
- mstankus
- mstankus@oba
-