I need to develop a small simple CMS to manage my news updates and articles written for the website. How should the articles be stored, considering they may be multiple pages. Should the text be stored in a database (MSSQL) or as an html file and filename information stored in the database?
Wouldn't storing the actual articles in the database take up a lot of server resources? Thanks,
Wouldn't writing/reading the article to/from an html file take up a lot of server resources?
I vote for storing the articles in the db.
Makes it easier to control which articles different user groups can read too.
If an article can be more than one page, use one table for article data, and another table for sections of an article (fk article id).
...values too large to fit in the row are stored in a collection of pages separate from the pages holding the data for the other columns of the row.
Although the user always works with text, ntext, and image data as if it is a single long string of bytes, the data is not stored in that format. The data is stored in a collection of 8-KB pages that are not necessarily located next to each other. ...
I.e. the value stored in the table isn't the text, it's a reference to the location where the text is stored
Simplified picture: sql server stores the "filename information"