Rob Fitzpatrick
ProgressTalk.com Sponsor
Version: 10.2B06
Runtime: AppServer on Linux or Windows
I was approached by a couple of developers who are prototyping a new application. I have few specifics, but they will be storing "large" amounts of XML messages in the database. For each message there would be a create, a few reads, and then little or no CRUD activity after that; historical data that would eventually be archived.
I will be meeting with them soon to drag out more details, including whether it makes sense to store this data in the DB at all, as opposed to flat files. I've just started my research but one notion I had was to store the data in a CLOB field. I know a bit about CLOBs from the docs but I haven't actually worked with them.
This app already has two databases so one possible approach is to add a third to store these messages and associated data. The downside, compared with adding the new table to one of the two existing DBs, would be incrementally more admin overhead from having another database. The upside would be avoiding the impact to the existing DB's transaction subsystem and buffer pool from moving large amounts of XML data through them.
I'm looking for any experiences, best practices, war stories, cautionary tales, etc. that you folks have to share re CLOBs. I am aware that they are ignored by dbanalys, at least in 10.2X. I haven't checked in 11.1 yet.
Runtime: AppServer on Linux or Windows
I was approached by a couple of developers who are prototyping a new application. I have few specifics, but they will be storing "large" amounts of XML messages in the database. For each message there would be a create, a few reads, and then little or no CRUD activity after that; historical data that would eventually be archived.
I will be meeting with them soon to drag out more details, including whether it makes sense to store this data in the DB at all, as opposed to flat files. I've just started my research but one notion I had was to store the data in a CLOB field. I know a bit about CLOBs from the docs but I haven't actually worked with them.
This app already has two databases so one possible approach is to add a third to store these messages and associated data. The downside, compared with adding the new table to one of the two existing DBs, would be incrementally more admin overhead from having another database. The upside would be avoiding the impact to the existing DB's transaction subsystem and buffer pool from moving large amounts of XML data through them.
I'm looking for any experiences, best practices, war stories, cautionary tales, etc. that you folks have to share re CLOBs. I am aware that they are ignored by dbanalys, at least in 10.2X. I haven't checked in 11.1 yet.