Re: Does it make sense to move this XML to a database?
Date: 5 Feb 2003 18:06:29 -0800
Message-ID: <32b8a689.0302051806.473b89bb_at_posting.google.com>
If this is the limit to your XML document, i.e. two tags, then transform it into a standard table. Functions for XML processing using XPATH and functional based indexes get slower as the table grows. I've tried storing Millions of XML records in a XMLType field.... indexing does become a nightmare. Simple because in XPATH querying, there are mutilple ways to write the same query. With Functuional indexes you have to write your query EXACTY the same as the syntax for the created index. If you didn't, Full Table Scan... ekkk!.
Cheers,
Greg Johnson
Brisbane, Australia.
efeigenb_at_alumni.tufts.edu (Figz) wrote in message news:<3758d0a5.0301300832.72d870a5_at_posting.google.com>...
> We keep a list of error numbers which each map to a user-friendly text
> description. Example:
>
> <ErrorDescriptor>
> <ErrorCode>1001</ErrorCode>
> <ErrorDescription>
> You entered an invalid email address.
> </ErrorDescription>
> </ErrorDescriptor>
> <ErrorDescriptor>
> <ErrorCode>1002</ErrorCode>
> <ErrorDescription>
> You entered a dollar amount less than zero.
> </ErrorDescription>
> </ErrorDescriptor>
>
> ....and so on, for every error. This list is now in the hundreds of
> errors. We're starting to look at better ways to store and map these
> error codes. Developers have started making new error codes when old
> ones already exist which probably match their needs but the xml takes
> so long to look through that it's easier just to create a new one.
>
> My questions are: Is it better to move this into a database table?
> At what point does the size of the xml file begin to degrade the
> performance? The problems with moving to a database table would
> include:
> · Time consuming to import all of them and make necessary database
> changes (Probably are a couple of ways to automate this though)
> · Will have to search and replace all existing use of error codes with
> calls to the database
> · More hits on our database
>
> Suggestions for designing a better error code/description system would
> be greatly appreciated. Any tips on what you have done in your
> experiences would be great. Thanks a lot!
Received on Thu Feb 06 2003 - 03:06:29 CET