default or NOT NULL for less overhead on insert
497150Mar 5 2007 — edited Mar 5 2007I have a very heavy insert table - about 30,000 r/s. Currenlty, there are no constraints - not to slow the inserts. But now I need to make one field NOT NULL because of the application inserts null values that nobody expected.
I was wondering on how to measure the overhead of making the column NOT NULL.
Also, if I add a default - is this going to provide faster inserts compare to creating Not Null constraint?
Ran some tests but nothing noticeble.
Thanks a lot ,mj