July 24, 2003 at 7:30 am
I am storing xml in a table, which is used later to reload an app. I figure fastest loading and retrieving would be to just store full xml text into a text or ntext column. So two questions, and pros or cons with text vs. ntext? Also, would it be better to parse out the xml for some reason, and store in database in a broken out 'relational' way, then rebuild xml later? Doesn't seem like it would be, but not sure if I'm missing something
Thanks!
July 24, 2003 at 7:54 am
Between TEXT and NTEXT: if you predict or absolutely know that your data will contain UNICODE characters, use NTEXT. Otherwise, DON'T, use TEXT.
--
Regarding parsing it out: Really the only reason you'd want to parse out the XML config file into separate fields is if your application heavily queries particular config fields. Sounds like your app is loading config information from the XML, though, so I doubt you'd have any need to store the XML in anything other than TEXT.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply