This means in versions before 9i, if the rowlength exceeds db_block_buffers then row chaing will take place if data is inserted to full capacity of column..
If inserted larger than db_block_size, then yes. The idea is to have a block size large enough to accomidate your rows. Remember, storage and performance go hand in hand.
Originally posted by grjohnson If inserted larger than db_block_size, then yes. The idea is to have a block size large enough to accomidate your rows. Remember, storage and performance go hand in hand.
Thanks for the reply..
But in case of large and wide (many columns especially with with varchar2) tables it is difficult to control row length below db_block_size.
I have few tables which stores medicine procedures and diagnosis, and it difficult to chop table in two different tables.
and these tables row length is more than db_block_size..
Unfortunatly not, if using Oracle server < 9i, your only alternative (if it really is affecting performance is create a new database with a larger block_size). It depends on the impact of the system, sure it's very undesirable. How many records are in the table etc?
Bookmarks