From: "Geo" 

"Ellen K."  wrote in message
news:re4g11d1fni607bkce9s8agsifr965gfpo{at}4ax.com...
> Honestly I don't see what they need SQL Server for this for, it's just
> gonna track our helpdesk tickets.  They could put that in an Access
> database.   (We have fewer than 1000 employees.)

I know what you mean. I have people ask about using sql for the backend for
a website when we have sites that get 100X the traffic and 1000X the data
they see running on an access db.

Some people simply have no concept of how to gauge requirements so they
just over engineer it. I did that when I built the bridge in my driveway. I
needed a bridge that could handle a car, maybe a 5 ton rating. I ended up
building a bridge that was rated for 25 tons.

The difference between my bridge and a website is significant though, my
bridge cost me 40% extra to overengineer, a website could cost 2500% more
due to the licensing requirements so it's a little more important to try
and gauge the requirements in that case.

Geo.

--- BBBS/NT v4.01 Flag-5