>HI,
>
>I am starting on the long process of documenting of all the existing data in a client's app for the purpose of transitioning it to another system. This will become part of an RFP requirements document. Of course, I would like to not look like a "doorknob" to outside suppliers when they read the document. But I am sometimes at a loss for words for certain items - perhaps those who have done this a lot will know the current terms for these items - I have not had to do this before.
>
>For my table definitions, I was going to have the following columns in the document. Most are straightforward:
>
>Name: column name
>Size/Type: N(5)
>Description: put in to help developer understand the column - NOT going to put a description in for something obvious like "Lastname"
>Validations: column describing validations over and above if just required etc.
>
>Here is the one I not sure of: I want to have a column that shows if the field is required (R) or needs to be encrypted (EC) or has a default value (Def) or any combination of those. Would it be correct to call that column Attributes or does that denote something else?
>
>Thanks,
>Albert

I would add NULL and INDEX, while index can be an expression that contains multiple fields, then it would make sense to Mention this separately.
Perhaps an indicator, which field is the primary key. Also interesting for foreign keys to mention which Primary key (Table.Field) they reference and if it is a 1:1 or 1:n or n:n relationship.

Why not make a column for each Attribute separately, that could be easier to read/maintain?

Name/Type/Description/NULL/REQUIRED/DEFAULT/ENCRYPTED/INDEX