Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Customer requested support for extraction and scripting of extent size and next size index storage properties.
Exampel:
create table ivan.tbl_B (a int, b int, c varchar(20), d int, e date, f bigint) GO CREATE INDEX idx_tbl_B_01 on ivan.tbl_B (b) using btree DISABLED extent size 32000 next size 16000 GO CREATE UNIQUE INDEX idx_tbl_B_02 on ivan.tbl_B (d desc, f asc) FILLFACTOR 77 IN rootdbs FILTERING WITHOUT ERROR extent size 64000 next size 32000 GO
Extraction & scripting of indexes Extent size and Next size properties now complete. There has been some modifications to the extraction to correct index owner been set to the table owner property. It is now correctly setting the table owner property to the table's owner.
I used the above example and should note that the FILLFACTOR <1-99>, IN <dbspace> & FILTERING WITHOUT ERROR properties are not been extracted and scripted. These properties do not exists in the index catalog tables.
Verified the extraction and scripting of extent size and next size index storage properties in 18.0.10-2
Verified the extraction and scripting of extent size and next size index storage properties in 18.0.10-2
Issue #15201 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v18.0.11 |
| No time estimate |
Extraction & scripting of indexes Extent size and Next size properties now complete. There has been some modifications to the extraction to correct index owner been set to the table owner property. It is now correctly setting the table owner property to the table's owner.
I used the above example and should note that the FILLFACTOR <1-99>, IN <dbspace> & FILTERING WITHOUT ERROR properties are not been extracted and scripted. These properties do not exists in the index catalog tables.