By | 2020-03-04


Another one of the database options which doesn’t serve any real purpose. As shown in this video the setting is overridden by session level settings so it doesn’t make sense to set it at Database level. This option default the NULLAbility of columns when creating the table or altering it. When set to off it defaults new columns to NOT NULL but unfortunately it only works at the session level and not the database level.

Like AUTO UPDATE STATS you don’t want to rely on this setting. In fact best practice dictates that you explicitly call out the NULLABILITY of columns when creating them.

Need more information? Visit https://www.enabledbusinesssolutions.com

To know more about Jayanth Kurup visit http://www.jayanthkurup.com

Jayanth is a Microsoft SQL Server trainer / consultant with over 15 years’ experience. He has worked with companies like Microsoft, IBM, HCL, Wipro, Well Fargo, Zeomega and many more. He is based out of Bangalore and a very active member of the SQL Server Community. In this channel he covers complex topics related MS SQL Server , PowerBI , Azure , AWS , Powershell, SSIS , SSAS , SSRS , Machine Learning , AI , etc

You can also reach Jayanth via his LinkedIn profile below www.linkedin.com/in/jayanth-kurup

Category: Uncategorized

About admin

This post was written by Jayanth Kurup. A Microsoft SQL Server Consultant and Trainer based out of Bangalore, India. Jayanth has been working on MS SQL Server for over 15 years. He is a performance tuning and Business Intelligence expert. Having worked with companies like Microsoft, DELL, Wells Fargo, Thomson Reuters and many other fortune 100 companies. Some other technologies Jayanth works on include Microsoft Azure, PowerBI, Python and AWS. When he isn’t consulting or training, Jayanth like to travel, paint and read. He is also very active in social causes and the founder of Enabled Business Solutions. Visit his company by clicking the link in the menu or email him directly.