asked on Access vs. XML
I have an ASP .NET website that queries an xml file using LINQ to construct some pages. I'm considering using Access to do this since some of the queries are becoming quite complex.
a. Will Access give me the performance boost I'm seeking?
b. Will it make code easier to maintain?
c. Are there any caveats to watch out for?
a. Will Access give me the performance boost I'm seeking?
b. Will it make code easier to maintain?
c. Are there any caveats to watch out for?
XMLASP.NETMicrosoft Access
Last Comment
Gustav Brock
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks to you all. That makes a lot of sense. XML is a flat file. Indices are not being used when a queried.
All queries start at the top of the file and read every record all the way to the end of the file. :(
Also, doing join queries are a nightmare in XML.
I think I will definitely explore Access. It has to be a better solution than XML.
BTW - Construct is just another word for 'build '
All queries start at the top of the file and read every record all the way to the end of the file. :(
Also, doing join queries are a nightmare in XML.
I think I will definitely explore Access. It has to be a better solution than XML.
BTW - Construct is just another word for 'build '
Then the performance of querying does not really matter, cause writing files to disk is much slower.
ASKER
Ste5an,
Thanks for the comment. I have one last comment.
True, writing to disk can be slow. To be more specific; writing to a database is much slower than writing to XML because database updates require update to indexes, etc. which can make lengthen the updating process depending of the number of rows and columns to be updated. XML; on the other hand is pretty straightforward, just append the data to the file. However, in my situation it does not matter.
a. The data, for the general user, will be read only . Admin will be the only user updating the data.
Thanks for the comment. I have one last comment.
True, writing to disk can be slow. To be more specific; writing to a database is much slower than writing to XML because database updates require update to indexes, etc. which can make lengthen the updating process depending of the number of rows and columns to be updated. XML; on the other hand is pretty straightforward, just append the data to the file. However, in my situation it does not matter.
a. The data, for the general user, will be read only . Admin will be the only user updating the data.
writing to disk can be slow.
In general, that is not the case. Writing a plain file is pretty fast.
All queries start at the top of the file and read every record all the way to the end of the file. :(
Also, doing join queries are a nightmare in XML.
That is exactly the point. And that is what the database engine solves by indexing the data and caching the data for multiple reads.
/gustav
That seems to cover it.
Can you give a small sample?