| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
Hi, we are currently working on a feasibility study in the public sector. Currently they use VSAM/ISAM data files where they store their data in binary format (VERY old applications, all Assembler). E.g. they store a birthdate in a 2 bytes format to save disk space ! All together, they now have 150 GigaBytes (!) of data, mostly in this compressed formats. Single files are up to 20 GB compressed. They want to go to client/server and databases. One of their biggest concerns is their huge amount of data (they reckon to multiply by 2-20 from today's GB if they use an RDBMS). What will we offer in the future (faster backup/restore...) to cope with such amounts of data ? (Rdb=VLDB...). How does the competition do (from Oracle/Informix to DB2) ? What about references (e.g. the largest Rdb database on the planet) ? Any help is appreciated, /Andreas
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1306.1 | NOVA::DIMINO | Fri Oct 29 1993 00:07 | 15 | ||
> What will we offer in the future (faster backup/restore...) to cope > with such amounts of data ? (Rdb=VLDB...). 150 Gbytes is not unreasonable for an Rdb DB. Backup/restore isn't a problem. We can backup 150 Gbyte in about 4 hours given the hardware, and we can do that today. If backup/restore is an issue, all the others will find it hard to compete, their system's costs will be much higher for the same performance, if they can achieve it at all. You don't have to sell futures with Rdb. I don't know what the largest Rdb database on the planet is. But in a few years 150 Gbyte won't be considered all that special. -lou | |||||
| 1306.2 | Don't force client to move what they don't need to move ... | ACESMK::RLEE | Fri Nov 19 1993 23:12 | 20 | |
And on the other hand:
** Don't discount how much they love their legacy system ...
Just completed the feasibility phase of a data warehouse project where
DB Integrator was used to connect thru RdbAccess for RMS to VSAM and
ISAM ASCII formatted files thru an Interlink (TM) TCP/IP to SNA
gateway. I didn't have a lot of time on this project -- but one of the
open issues was whether or not EBCDIC files could be autotranslated
by the Interlink (TM) Gateway before transmission.
Alternative? DECnet/SNA Data Transfer Facility (DTF) should handle the
binary translation problem for RdbAccess for RMS in a DECnet protocol
environment.
Beauty of DB Integrator? It makes the legacy files look like SQL
tables. With products like the next DEC Data Distributor, the whole
process of transporting the legacy data becomes an automation dream.
2 cents worth ... /bob lee/
| |||||