CLOBs

I decided to use CLOBs (Character Large Objects) with a modern RDBMS to save these documents.

Since the RDBMS supported a Java API to insert and retrieve CLOBs, this was a very easy task.

Many database systems allow you to store XML data as CLOBs or "shred" the data into relational tables.

Even if the Chinese or Russian documents were inserted as BLOBs, they cannot be serialized as CLOBs or CHAR-types without giving this error.

Side tables can avoid much of the XML parsing for CLOBs and can often make CLOB queries 100 times faster or more.

This means that XML is either stored in files, stored wholesale in database CLOBs, or shredded into distinct columns.

It scales with the database, and XML-specific optimizations give it better performance than CLOBs.

At present, stored procedures and user-defined functions do not have support for XML as a parameter, but they can easily be passed as CLOBs.

Smart LOBs consist of character large objects (CLOBs) and binary large objects (BLOBs) data types.

Figure 5 shows the query performance (elapsed time) of all five test queries for both pureXML and CLOBs.

The current strategy of storing marked-up text in BLOBs, CLOBs, and VARCHARs isn't nearly as natural or efficient.

That's a nice improvement over working with XML data as CLOBs or VARCHARs, which require maximum lengths.

Don't log large data objects (CLOBs, DBCLOBs, and BLOBs) unless necessary.

Unstructured storage using CLOBs (also know as schema-less storage)