[AccessD] On DB Bloat, Bad DB Design, and various

DWUTKA at marlow.com wrote On 5/26/2004 2:29 PM:

>Francisco, first of all, I am honestly not sure how SQL server deals with
>character fields and their 'lengths'.  In Access, setting a field to a 255
>width does not make the storage space requirement any larger then if it is
>set to 50, unless someone types 51 or more characters.  Does SQL Server take
>up the 'empty' space regardless?  Again, I'm not sure.
>
>  
>
No, they do not take more space, however you must calculate the number 
of characters you "expect" per field per table in order to set an 
estimated growth for your database.  This is one of things that usually 
gets skipped w/ many Access developers because generally db's might be 
no bigger than a few megs.  However if it is expected that the db will 
grow, you'll want to take that consideration for your client so they can 
properly allocate 100/200/300gig hdd's as needed.

>My analogy to a gas tank was not off, you just didn't make the connection I
>was trying to make.  The size of the gas tank is the maximum length of a
>text field, or 255.  That is what JET has designated as a test field max.
>The amount of gas you put in, is the limit YOU assign to the field.  Does it
>make sense to not give them a full tank of gas? 
>
maybe you chose the wrong analogy, didja ever think that? :>
The reason that still doesn't make sense, is because I or whoever 
borrows the car can always re-fill the tank at any gas station.  Perhaps 
if you said I took an explorer and fitted it w/ a Ford Festiva Tank, 
wich only filled up to about 8 gallons....

> Putting a larger gas tank
>in, is like going to SQL Server.  If it's necessary, then do it.  If it's
>not, then don't.
>
>  
>
No that's like going from a 4 banger to a full 10 cylinder HEMMI.


-- 
-Francisco