You can use the output of this script to decide whether the definition of the candidate columns could be changed to enforce a NOT NULL constraint. By not allowing NULL values, you can help simplify queries and avoid data ambiguity.
To use the script, simply execute it against a target database. In the event that the account you’re running the script under doesn’t have SELECT permission on a table, that table is reported through the @SkippedTablesT table variable (so you know the table was skipped).
