Hi all,

 

We have one of our company sites running about 230 static pages which could
be inserted into a database, our "CLEVER" CIO has now thought that maybe we
should be looking at a database option, but he now has asked me to produce a
document why we should move from static pages (being financial results
contact details etc) to a dynamic asp.net or asp environment.

 

I was wondering if any of you have been through this and have any reasons to
add to my growing list , anything is fine so please send away!

 

Regards,

Carlos Magalhaes

 

Been there, done that, still waiting for the t-shirt. Just my
opinion but storing static pages in a database is a waste of time
and resources. On the other hand, if you store the information that
is on your static pages in a database and rewrite your pages with
placeholders for the data you gain a lot of value. Anything that is
used more than once is guaranteed to be the same since it comes from
the same place. Updates and maintenance are much easier since you
only have one place to update data. Something like a company's
contact information may be on every page. With 230 pages there's a
good chance that there's a typo on at least one page. If all the
pages pull the contact info from one place in the database it's
going to be the same on each page. If the address changes you only
have to change it once in the database and every page is updated.
With static pages you'd have to change the address on all 230 pages
with a big chance of a typo on some pages and possibly missing a
page or two that will retain the old address. It's a lot of work to
design and change to dynamic pages using a database. If your pages
don't change much or you don't reuse anything between pages it's
probably wasted work. If you have a lot of repetition and change it
can save tremendous amounts of maintenance work.
Will

>-----Original Message-----
>From: Carlos Magalhaes [mailto:CarlosM@t...]
>Sent: Tuesday, January 28, 2003 1:12 AM
>To: ASP.NET
>Subject: [aspx] Static or Dynamic
>
>
>Hi all,
>
>
>
>We have one of our company sites running about 230 static
>pages which could
>be inserted into a database, our "CLEVER" CIO has now thought
>that maybe we
>should be looking at a database option, but he now has asked
>me to produce a
>document why we should move from static pages (being financial
results
>contact details etc) to a dynamic asp.net or asp environment.
>
>
>
>I was wondering if any of you have been through this and have
>any reasons to
>add to my growing list , anything is fine so please send away!
>
>
>
>Regards,
>
>Carlos Magalhaes
>
>
>
>
>

Dynamic sites are a mix of static and dynamic content down to the page
level, if you have say a header that you want in a lot of places, using
an include in that case to store the header in one place for all pages
that need it is usually much less painful then storing it in a database,
other things like content that's always changing is better off being
dynamic, like the news stories on cnn. I don't know how cnn is built but
I would have the header in an include and the stories in a database.


-----Original Message-----
From: Will Swim [mailto:wswim@p...] 
Sent: Tuesday, January 28, 2003 12:32 PM
To: ASP.NET
Subject: [aspx] RE: Static or Dynamic


Been there, done that, still waiting for the t-shirt. Just my opinion
but storing static pages in a database is a waste of time and resources.
On the other hand, if you store the information that is on your static
pages in a database and rewrite your pages with placeholders for the
data you gain a lot of value. Anything that is used more than once is
guaranteed to be the same since it comes from the same place. Updates
and maintenance are much easier since you only have one place to update
data. Something like a company's contact information may be on every
page. With 230 pages there's a good chance that there's a typo on at
least one page. If all the pages pull the contact info from one place in
the database it's going to be the same on each page. If the address
changes you only have to change it once in the database and every page
is updated. With static pages you'd have to change the address on all
230 pages with a big chance of a typo on some pages and possibly missing
a page or two that will retain the old address. It's a lot of work to
design and change to dynamic pages using a database. If your pages don't
change much or you don't reuse anything between pages it's probably
wasted work. If you have a lot of repetition and change it can save
tremendous amounts of maintenance work. Will

>-----Original Message-----
>From: Carlos Magalhaes [mailto:CarlosM@t...]
>Sent: Tuesday, January 28, 2003 1:12 AM
>To: ASP.NET
>Subject: [aspx] Static or Dynamic
>
>
>Hi all,
>
>
>
>We have one of our company sites running about 230 static pages which 
>could be inserted into a database, our "CLEVER" CIO has now thought
>that maybe we
>should be looking at a database option, but he now has asked
>me to produce a
>document why we should move from static pages (being financial
results
>contact details etc) to a dynamic asp.net or asp environment.
>
>
>
>I was wondering if any of you have been through this and have any 
>reasons to add to my growing list , anything is fine so please send 
>away!
>
>
>
>Regards,
>
>Carlos Magalhaes
>
>
>
>
>
>---
>Change your mail options at http://p2p.wrox.com/manager.asp or to 
>unsubscribe send a blank email to