You don't have to create a trigger for each column. One trigger per table can handle all columns in it.

>
>As I am redesigning my SQL Server database and see that I may have to "enforce" that all foreign key fields have only value of NULL when user does not assign a value. Since the database gets records from various applications (VFP, ASP.NET, iOS, etc.) I have to "enforce" this rule at the DB and therefore create a trigger for every field in every table. This means that I will have probably up to 200 triggers. Is this a normal/acceptable/good practice?
>
>TIA