Lists Home |
Date Index |
We're looking at a content management system, which stores all of the content/metadata in a single, 1 MB XML file on disk or as separate records (for each parent element) in a two-field table in SQL, out-of-the-box. Based on our rough content estimates, however, we can see this file growing to over 100 MB easily. The CMS provider says that anything over 30 MB should use the SQL backend.
The one thing that we do not like is the schema/data model (or lack of) for the SQL storage option. Coming from the relational camp, this seems odd to us, and even on disk, hierarchically, it seems to make more sense to break up this single XML file into smaller files (per parent element) in a directory structure with an index.
...But then again, you guys are the experts :)
Can anyone see any problems with this storage architecture from a performance/stability/scalability standpoint?
Thanks in advance!