SheSaidImaPregy 28 Veteran Poster

I am creating a site where normally I would store this kind of information in a database. It is information that will most likely never.. EVER be changed again unless it needs administrative modification. Just possibly deleted ^^

I was thinking about storing a link in a database that leads to a text file, which from there I could read the text straight onto the page. It would provide a lot less data being sent from the SQL server, not to mention quicker response time from the SQL server from a very populated database traffic community.

What would be a good way to give access to a user for his/her stories that can contain upwards of 10,000 characters, or upwards of 20-30 pages in a word document.

The user will need to be able to edit the data anytime he/she wishes, however this rarely, if ever happens.

I was thinking about storing the information in the database for one week, which gives enough time for the user to edit. Then, after 1 week goes by, to have the stories transfered to a data file, like a txt file or xml, and not be editable there after.

Please share thoughts on how to store static information. Maybe even create a new aspx page with the static information? However, this is out of my scope of experience, dynamically creating aspx pages with master pages as well.

Share thoughts