• michael.kaufmann (7/14/2010)


    My gutt told me to go for option 1, but not because of it running faster, but because I wondered why one would change a non-nullable column to nullable (especially when it holds the login name).

    That's why I went with Option 1. The Business had already determined that the LOGIN column must be non nullable. While I'm on vacation I don't expect my guys to make these kinds of changes, but even if they did, replacing a NOT NULL column with a NULLABLE one would incur more wrath than they'd ever want to run into.



    --Mark Tassin
    MCITP - SQL Server DBA
    Proud member of the Anti-RBAR alliance.
    For help with Performance click this link[/url]
    For tips on how to post your problems[/url]