Re: Largest DB in Syabse and Oracle - Startup size

the prob with large dbs is not usually thru put, but time to reorg, create indexes, recover etc etc. a single-tape-drive restore can take 2 or 3 hrs per gig (v4.9.2). even dbms's like db2 restore around 2 gigs per hour (depending on indexes).

large dbs require special tricks (such as off-line reorg, followed by replication from prod to re-orged db, followed by db renames to get new version in prod) which are a pain in the butt to design & execute.

personally i would not have a 200gig db in sybase (yet) unless i really had no option.

steve.

In <3a9pof$cq1_at_c2.eunet.co.at>, "Michael R. Fronheiser" <eb187_at_cleveland.freenet.edu> writes:
>Greetings,
>
>I keep seeing posts asking which DB is better, Sybase or Oracle?
>I guess my test is the database that can support Large amounts
>of data with acceptable throughput.
>
>Has anyone created a database larger that 200 Gig.? Last summer I
>helped start up a system of that size. I am sure it has increased
>in size since then, but that was the initial size. For the most
>part I would say that we did not have any significant performance
>issues. We used Sybase 4.9.? on a Dec VAX 65??.
>
>Just woudered,
>
>Mike
>
>
  Received on Tue Nov 15 1994 - 23:00:00 CET