The question is unclear. Are you asking about storing data in an XML file instead of a DB or storing data inside a DB but as XML type. Further muddying is the example of .net config file …

Dec 11, 2020 · 16 JSON and XML are less efficient than pure binary, but what you aren't considering is that they (JSON/XML, and some other formats like YAML) are standardised, …

Store everything in a relational DB. Store everything in a native XML DB. Store data in two separate DBs, XML in native XML and metadata in relational. Option 3 is probably the …

XML is only bad because many people abuse it for things out wasn't designed for. If you don't need your data to be readily extensible (i.e. the scheme is used by multiple parties who need …

Apr 26, 2016 · Explore efficient ways to store key-value pairs in a database, including best practices and potential pitfalls.

Mar 3, 2011 · I could see it being used to store XML that isn't queried that much though, say storing the full XML document in a XML data type, but having the searchable fields (keys) …

There are a couple of answers on SE comparing single-row table vs. name-value-pair table used for config settings, but I haven't seen anyone arguing for using XML (or JSON) as a name …

In both cases I used XML files to store the data. In the first one, which was on the 2.0 Framework, I used the old style XML parsing calls to look up data. For the newer one, on the 3.5 …

Apr 30, 2013 · It seems my options are Store the data in XML. Compile the XML file as an assembly resource. Load data as needed, store loaded data into a Dictionary for repeat-use …

18 It is clear that using some kind of Version Control System for storing docs is a nobrainer. The more interesting part of the question is if it is good idea to store documents in the SAME …