- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Calculate storage requirements for an index
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 06:57 PM
тАО11-30-2004 06:57 PM
Calculate storage requirements for an index
I wish to create an index for a table and place the index in a new tablespace. Lets say I want to index only one column
How do I determine the SIZE requirements for the new tablespace?
CREATE TABLESPACE "TABLE" DATAFILE '/users/data/Index_tbs7.dbf' SIZE ????M
For the index itself, what should the initial size be?
Note that the table is maintained automatically and will never grow in size
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 08:08 PM
тАО11-30-2004 08:08 PM
Re: Calculate storage requirements for an index
You say it will never grow... what about updates ?
What is cardinality for index columns ? How many indexed columns ?
There are many questions related to index estimation size. None will be as efficient as a test : Create a copy of the table and create index. Of course it's not usable if your table is too big. In that xase, some tool may help you. For example, Toad estimate index size before creation and some other may do the same.
Regards,
Fred
"Reality is just a point of view." (P. K. D.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 09:51 PM
тАО11-30-2004 09:51 PM
Re: Calculate storage requirements for an index
is it true that you are trying to create a tablespace for ONE index???
The normal trend is to create Locally managed tablespaces with uniform extents (depending whether it is small, medium, large or xlarge) and stop worrying about sizing of tables as such!
if you need any further info, please let us know.
regards
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 10:16 PM
тАО11-30-2004 10:16 PM
Re: Calculate storage requirements for an index
Regards,
Fred
"Reality is just a point of view." (P. K. D.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 11:16 AM
тАО12-01-2004 11:16 AM
Re: Calculate storage requirements for an index
I am using Oracle 7.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 08:15 PM
тАО12-01-2004 08:15 PM
Re: Calculate storage requirements for an index
If the table is not to grow, it's simple: put the same size of the table for the index. But, ever if the table grows, size of the index will never be a problem since you can rebuild it with a new size:
alter index
storage (initial
This is why I recomend you to use more 50% of the table size for the tablespace/datafile!
You can determine the size of the table with this SQL:
select segment_name, sum(bytes) ebytes
from dba_extents
where segment_name =
group by segment_name;
Best Regards,
Eric Antunes