Rows per page

Hi all, We are running IDS 9.21 UC6 on Solaris 8. I have a table which we are adding 2/3 news columns to. This will increase the size of a row to greater than 2Kb ie. one page. Can anyone tell me what affect this will have on the space required to store the data. I understand that retrieval will be affected but is storage/space also affected. Regards, Karen

Karen As much of the record as will fit on a page will go on the first free page along with a pointer to the remainder. The rest of the record will occupy part of a 'remainder page' pointed to by the first part. The remainder page will only hold remainders and each new record will start on a new page. Keith -> -----Original Message----- -> From: Egan Karen-.... [mailto:Karen.Egan@motorola.com] -> Sent: Monday, March 03, 2003 1:16 PM -> To: ids@iiug.org -> Subject: Rows per page [550] -> -> -> Hi all, -> -> We are running IDS 9.21 UC6 on Solaris 8. I have a table -> which we are adding 2/3 news columns to. This will increase -> the size of a row to greater than 2Kb ie. one page. -> -> Can anyone tell me what affect this will have on the space -> required to store the data. I understand that retrieval will -> be affected but is storage/space also affected. -> -> Regards, -> Karen -> ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** **

Karen, I am not familiar with IDS 9.2 or .4 yet, but on 7.31.... if you are adding columns to the end of the table, you will be working with "table versioning"/in-place alter issues. As you add new rows to the table, they will be the new size. As you update old rows, they will expand to the new size. However any old rows that are not updated (just reading/selecting won't change them) will remain the old size until they are updated by users or "fake updated" by you, or hit by a table reorg. If you reorg the table (unload/rebuild/reload), you will experience a space consumption potentially greater than you thought would happen as each row that had not been touched will expand to the new size. you may avoid this by running an update SQL to hit all rows (where 1=1) now instead of seeing the space hit later. We almost got caught by this on a nearly 32GB table. We planned the reorg weekend with space in mind for the current size and it's fragmentation need. During the weekend, we almost got slaughtered... the reorg took longer to expand all the rows and of course it took up more space. We had tested this, but were not given enough time to fully test.... but we survived. Again, I don't know if this is true in 9.x, but it is in 7.3 Norma Jean -----Original Message----- From: keith.simmons@bbslimited.co.uk [mailto:keith.simmons@bbslimited.co.uk] Sent: Monday, March 03, 2003 8:40 AM To: ids@iiug.org; forum.subscriber@iiug.org Subject: RE: Rows per page [552] Karen As much of the record as will fit on a page will go on the first free page along with a pointer to the remainder. The rest of the record will occupy part of a 'remainder page' pointed to by the first part. The remainder page will only hold remainders and each new record will start on a new page. Keith -> -----Original Message----- -> From: Egan Karen-.... [mailto:Karen.Egan@motorola.com] -> Sent: Monday, March 03, 2003 1:16 PM -> To: ids@iiug.org -> Subject: Rows per page [550] -> -> -> Hi all, -> -> We are running IDS 9.21 UC6 on Solaris 8. I have a table -> which we are adding 2/3 news columns to. This will increase -> the size of a row to greater than 2Kb ie. one page. -> -> Can anyone tell me what affect this will have on the space -> required to store the data. I understand that retrieval will -> be affected but is storage/space also affected. -> -> Regards, -> Karen -> ************************************************************************ ********** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ************************************************************************ ********** --openmail-part-39e3a146-00000002 Content-Type: application/rtf Content-Disposition: attachment; filename="BDY.RTF" ;Creation-Date="Mon, 3 Mar 2003 10:09:20 -0600" Content-Transfer-Encoding: base64 {\\rtf1\\ansi\\ansicpg1252\\fromtext \\deff0{\\fonttbl {\\f0\\fswiss Arial;} {\\f1\\fmodern Courier New;} {\\f2\\fnil\\fcharset2 Symbol;} {\\f3\\fmodern\\fcharset0 Courier New;}} {\\colortbl\\red0\\green0\\blue0;\\red0\\green0\\blue255;} \\uc1\\pard\\plain\\deftab360 \\f0\\fs20 Karen,\\par I am not familiar with IDS 9.2 or .4 yet, but on 7.31....\\par if you are adding columns to the end of the table, you will be working with "table versioning"/in-place alter issues. As you add new rows to the table, they will be the new size. As you update old rows, they will expand to the new size. However any old rows that are not updated (just reading/selecting won't change them) will remain the old size until they are updated by users or "fake updated" by you, or hit by a table reorg.\\par \\par If you reorg the table (unload/rebuild/reload), you will experience a space consumption potentially greater than you thought would happen as each row that had not been touched will expand to the new size. you may avoid this by running an update SQL to hit all rows (where 1=1) now instead of seeing the space hit later.\\par \\par We almost got caught by this on a nearly 32GB table. We planned the reorg weekend with space in mind for the current size and it's fragmentation need. During the weekend, we almost got slaughtered... the reorg took longer to expand all the rows and of course it took up more space. We had tested this, but were not given enough time to fully test.... but we survived.\\par \\par Again, I don't know if this is true in 9.x, but it is in 7.3\\par Norma Jean\\par \\par \\par \\par -----Original Message-----\\par From: keith.simmons@bbslimited.co.uk\\par [mailto:keith.simmons@bbslimited.co.uk]\\par Sent: Monday, March 03, 2003 8:40 AM\\par To: ids@iiug.org; forum.subscriber@iiug.org\\par Subject: RE: Rows per page [552] \\par \\par \\par Karen\\par \\par As much of the record as will fit on a page will go on the first free page\\par along with a pointer to the remainder. The rest of the record will occupy\\par part of a 'remainder page' pointed to by the first part. The remainder page\\par will only hold remainders and each new record will start on a new page.\\par \\par Keith\\par \\par -> -----Original Message-----\\par -> From: Egan Karen-.... [mailto:Karen.Egan@motorola.com]\\par -> Sent: Monday, March 03, 2003 1:16 PM\\par -> To: ids@iiug.org\\par -> Subject: Rows per page [550] \\par -> \\par -> \\par -> Hi all,\\par -> \\par -> We are running IDS 9.21 UC6 on Solaris 8. I have a table \\par -> which we are adding 2/3 news columns to. This will increase \\par -> the size of a row to greater than 2Kb ie. one page. \\par -> \\par -> Can anyone tell me what affect this will have on the space \\par -> required to store the data. I understand that retrieval will \\par -> be affected but is storage/space also affected.\\par -> \\par -> Regards,\\par ->