Entry Riley:1993:DMO from dectechj.bib

Last update: Thu Sep 27 02:13:54 MDT 2018                Valid HTML 4.0!

Index sections

Top | Symbols | Math | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

BibTeX entry

@Article{Riley:1993:DMO,
  author =       "Mark F. Riley and James J. {Feenan, Jr.} and John L.
                 {Janosik, Jr.} and T. K. Rengarajan",
  title =        "The Design of Multimedia Object Support in {DEC Rdb}",
  journal =      j-DEC-TECH-J,
  volume =       "5",
  number =       "2",
  pages =        "50--64 (or 50--65??)",
  month =        "Spring",
  year =         "1993",
  CODEN =        "DTJOEL",
  ISSN =         "0898-901X",
  bibdate =      "Thu Mar 20 18:15:43 MST 1997",
  bibsource =    "http://www.math.utah.edu/pub/tex/bib/dectechj.bib",
  URL =          "ftp://ftp.digital.com/pub/Digital/info/DTJ/v5n2/The_Design_of_Multimedia_Objec_01oct1993DTJA05P8.ps;
                 http://www.digital.com:80/info/DTJA05/DTJA05SC.TXT",
  abstract =     "Storing multimedia objects in a relational database
                 offers advantages over file system storage. Digital's
                 relational database software product DEC Rdb supports
                 the storing and indexing of multimedia objects ---
                 text, still frame images, compound documents, audio,
                 video, and any binary large object. After evaluating
                 the existing DEC Rdb version 3.1 for its ability to
                 insert, fetch, and process multimedia data, software
                 designers decided to modify many parts of Rdb and to
                 use write-once optical disks configured in standalone
                 drive or jukebox configurations. Enhancements were made
                 to the buffer manager and page allocation algorithms,
                 thus reducing wasted disk space. Performance and
                 capacity field tests indicate that DEC Rdb can sustain
                 a 200-kilobyte-per-second SQL fetch throughput and a
                 57.7-kilobyte-per-second SQL\slash Services fetch
                 throughput, insert and fetch a 2-gigabyte object, and
                 build a 50-gigabyte database.",
  acknowledgement = ack-nhfb,
  classcodes =   "C6160D (Relational DBMS); C5320K (Optical storage);
                 C7250 (Information storage and retrieval)",
  classification = "C5320K (Optical storage); C6160D (Relational DBMS);
                 C7250 (Information storage and retrieval)",
  keywords =     "200 Kbyte/s; 50 Gbyte; 57.7 Kbyte/s; audio; Audio;
                 buffer manager; Buffer manager; compound documents;
                 Compound documents; databases; DECRdb; frame images;
                 indexing; Indexing; Jukebox configurations; jukebox
                 configurations; Multimedia object support; multimedia
                 object support; multimedia systems; optical disc
                 storage; optical disks; page allocation algorithms;
                 Page allocation algorithms; relational; software
                 packages; SQL fetch; SQL fetch throughput; standalone
                 drive; Standalone drive; still; Still frame images;
                 Storing; storing; throughput; Video; video; write-once;
                 Write-once optical disks",
  numericalindex = "Memory size 5.4E+10 Byte; Byte rate 2.0E+05 Byte/s;
                 Byte rate 5.77E+04 Byte/s",
  thesaurus =    "Multimedia systems; Optical disc storage; Relational
                 databases; Software packages",
  treatment =    "P Practical",
}

Related entries