Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
up vote 2 down vote favorite
2

Our DB2 database(V9.7) has only defined one table space to store all the big object like xml. And xml size could be different. Some are about 2kb average. And some are 7kb average. So does it make sense to set the table space to use 32kb data page? How to judge it? I have once seen that one data page can only contain one xml row. Is that true?

Any advice is welcome!

share|improve this question

1 Answer

up vote 1 down vote

Check out the general answer I gave to you on your other question.

If you are storing your XML as a LOB, then I guess I'd see what is the common average size per table. If the average size is 4MB or less (which it sounds like), then you'd only need a 4K tablespace (see Space requirements for table, table 1).

If you are storing the XML as an XML data type in DB2, then you actually get some performance gains over LOB, especially if you inline the XML (and aren't doing updates to it all that often). This may be the best since you mention sizes less than 32K. You may wish to check out XML storage page for in-lining XML within the table vs outside for XML storage.

share|improve this answer
I am a bit hesitating to use inline to store the xml into the base table directly. As it said, it will be benefit to operate on the xml. But not normally it happens on non-xml columns.And the base table is defined on the table space with 4k data page. I could try to inline some small xml column though. – Clark Bao Aug 15 '12 at 23:55

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.