In addition, i can make searching easier if the content of all articles is in the DB (is this correct?), but then again, I'm worried about the issue of an oversized DB. Are my fears correct? If so, what should be the better implementation?
floorbamboo <[EMAIL PROTECTED]> wrote: Hi! I would like to ask how best to handle webpages in relation to databases. I ask this question because i can't decide if what is preferable: to keep webpages in their proper folders and link to these as separate pages (or as #include files), or to place the contents of webpages in databases and then "string" these to be presented as webpages. Placing the contents of files in DB seems to be easier maintenance- wise, but this way, the DB size will balloon easily, and i worry that this will make accessing the DB take much longer. Is this correct? What is preferable? Or what is the current practice? I have just started studying ASP (classic, along with introductory SQL, ADO, & JScript), and I haven't read an article on this matter yet. I hope somebody can point me to relevant documents. Thank you. Yahoo! Groups SponsorADVERTISEMENT --------------------------------- Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/AspClassicAnyQuestionIsOk/ To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. --------------------------------- Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now [Non-text portions of this message have been removed] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspClassicAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
