I thought I did reload, but I'll check. In the same way that a "unique column value" constraint must add an entry to the index for each row, does a "not null" constraint have to add an index entry for each row?
It's also possible that the "not null" constraints were loaded multiple times. (Ugh!) Thanks, Dennis ***** At 03:06 AM 5/3/02 -0400, you wrote: >At 01:46 AM 5/3/2002 -0400, Dennis Fleming wrote: > >>But... I noticed that at a customer this week, a table which had a file 2 >>size of 12mb and file 3 size of 8mb, jumped to 17mb for file 3 after the >>constraints where added??!!! >> >>This doesn't seem like very good design. Any suggestions? > >Dennis, > >I suggest that you RELOAD the database. > >Very Best Regards, > >Razzak. > > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l >================================================ >TO SEARCH ARCHIVES: >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Fax: 570 775-9797 ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
