October 13, 2011 at 1:14 pm
enforcing not null is always good on a table, and peformance.
But if i code side always ensure that null never happens(and there is no other way) should i leave the constraint of "allow nulls" checked then it wont "check"
hence nulls are not in the table, and the db doesnt have to take the time to do this "check"
isnt that a better approach?
October 13, 2011 at 1:17 pm
Please don't cross post. Point all responses here. http://www.sqlservercentral.com/Forums/Topic1190140-360-1.aspx
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply