database

[maxmangion]

I am planning to create a database to handle membership data for a local club.

I would like to ask for some tips regarding the following please:

1) is there any disadvantages in placing a scanned image for every member in his personal record ? Note there are about 800 members which means 800 images.

2) if it is not a problem to put the images, are there any guidelines which i shuld take care for these images during the design i.e. type of image, size, and any other property that my effect the performance in general.

Also if there are any additional guidelines/precautions for the overall performance which i should take care of I would appreciate that someone will point them out pls.

Thanks

 

[IMO]

Do NOT store the images in the database, this will bloat it. Take a look at the example to see how to create tables with the image path.

IMO

 

[Mark Wild]

Probably your biggest performance issue at the moment will be related to your table structure.

Have a good search for normalisation and see if any of the posts help you layout how best to store your data to minimise redundancy.