- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: How to judge a table need export/import?
Operating System - HP-UX
1753416
Members
5119
Online
108793
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-24-2004 12:48 AM
12-24-2004 12:48 AM
Re: How to judge a table need export/import?
Eric,
IMHO, monitoring table fragmentation is part of DBA's job, as far as disks fragmentation is part of Sysadmin's. Now both have some ways to deal with this problem.
Regarding DBA's job, it is now much better to go into 'alter table xxx move' process than export/import. This will help removing chained rows and too big high water marks (fragmentation itself could be avoided using, for example, local management and uniform extent size).
If your problem is high water mark, you should find a way to have a ratio between high water mark and real data size for which your performance seems to be no more acceptable. Then you can produce a script telling which tables reach this ratio and so need rebuild (move). Running it periodically will help keep better perfs.
Regards,
Fred
IMHO, monitoring table fragmentation is part of DBA's job, as far as disks fragmentation is part of Sysadmin's. Now both have some ways to deal with this problem.
Regarding DBA's job, it is now much better to go into 'alter table xxx move' process than export/import. This will help removing chained rows and too big high water marks (fragmentation itself could be avoided using, for example, local management and uniform extent size).
If your problem is high water mark, you should find a way to have a ratio between high water mark and real data size for which your performance seems to be no more acceptable. Then you can produce a script telling which tables reach this ratio and so need rebuild (move). Running it periodically will help keep better perfs.
Regards,
Fred
--
"Reality is just a point of view." (P. K. D.)
"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-24-2004 01:34 AM
12-24-2004 01:34 AM
Re: How to judge a table need export/import?
This doc is also not too bad ;)
Regards,
Fred
Regards,
Fred
--
"Reality is just a point of view." (P. K. D.)
"Reality is just a point of view." (P. K. D.)
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP