Some Dos and Dont's in designing website databases(dotnetslackers.com)
submitted by wisemx(8074) 4 years, 3 months ago
1. Choose the right data storage device ...
2 comments |category: Database |Views: 1 Tweet
tags: Database another
Add a live kick counter to your blog >>
You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:
Simply copy and paste this HTML into your blog post.
posted by crpietschmann(11.3k) 4 years, 3 months ago 0
um... This post is not correct. The first thing it says is "Do not use XML files as the sole data storage device, for XML files are not ideal for constant data operations (delete, insert, update).". I stopped reading after that. The best thing you can do when designing where your website will store its data is to build the data access layer using the provider model. This way you can always and easily change your mind and move you data to any store you want, and you wont be bound to your first choice of data storage.
Reply
posted by wisemx(8074) 4 years, 3 months ago 0
I've been developing against XML as a datasource since 1999 and have heard arguments from both sides, each with valid points. It is true some of the ASP.NET Start Kits function very well with XML datasources. And I've been doing some tricky stuff lately with Linq and XML, very fast and robust with no noticeable memory hit. For some tasks I have tested XML just doesn't hold up, but it is all in all a very handy data basket. </2.Cents>
All tags Your tags
Suggest a new category
dpeterson(1273)
Telerik(409)
fdub(381)
amit.jain(268)
BlackWasp(259)
RobertTheGrey(259)
jalpesh(252)
bsenoff(240)
KodefuGuru(227)
KMillerr(226)
wisemx(8074) 4 years, 3 months ago