The Content Services application component is a file server, but much of its superiority over conventional file servers stems from the fact that the data is not stored as files on disk, but as rows in a database. When a user accesses a file that is stored in Content Services, he is not reading or writing the server’s disk system: he is executing select,insert, update, and delete commands against a database.
The default method for storing Content Services data is as BLOBs. The release 10g database used for Oracle Collaboration Suite 10g can theoretically store terabyte-size BLOBs. There is therefore no effective limit to the size of the documents that can be stored within Content Services.
This technique enhances performance substantially, because the pattern of access to BLOB data tends to be very different to the pattern of access to other columns.
Consider a simple example of uploading all your music CDs into a database. Once you have identified the CD of interest, there will be a continuous read of 600MB as it is downloaded.
The Oracle BLOB data type lets the database administrator separate the one logical table
into two physical segments; one segment contains the small columns, the other contains the BLOB column. Each segment can be configured appropriately for its typical access and stored on devices optimized for this.
No comments:
Post a Comment