On what basis the size of any field in the table is decided.
-
As far as possible you want to design your database so that once columns have been created they do not need amending in the future. The nice people at Microsoft provided us with the VarChar field which allows our text based database field sizes to grow over time. With regards to integer fields you need a fairly good idea of how big the numbers are going to get as there are four different types of integer. With regards to:
Master Mind'z wrote:
Is there any standard or as per need?
The analysis phase should specify what column definitions are. My advice is to create a database where the columns are as future proofed as possible - this means avoid setting columns such as 'sales quantity' columns to tinyint. Also google your question as there will be pages dedicated to this area.
You always pass failure on the way to success.