- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Performance :SQLLoader Versus Select for Update
Operating System - HP-UX
1752692
Members
5669
Online
108789
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
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
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
тАО02-04-2004 03:48 AM
тАО02-04-2004 03:48 AM
Performance :SQLLoader Versus Select for Update
Hi,
I'm currently in front of a performance problem about a FETCH with an update in table ( 80 millions Records ) and this request commit 25 row per seconds.
SO I would like to now if
- I select all my record
-,insert them in a temporary table
-and finally reload with sqlldr the empty table with the updated records
that will be more efficient in term of performance than the update describe on top.
thanks in advance
LLB
I'm currently in front of a performance problem about a FETCH with an update in table ( 80 millions Records ) and this request commit 25 row per seconds.
SO I would like to now if
- I select all my record
-,insert them in a temporary table
-and finally reload with sqlldr the empty table with the updated records
that will be more efficient in term of performance than the update describe on top.
thanks in advance
LLB
J@Y
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 04:03 AM
тАО02-04-2004 04:03 AM
Re: Performance :SQLLoader Versus Select for Update
Like so many things, it depends. Are there indexes with the table that are getting rewritten with each update? Can you make sure your temporary table in on a different physical & logical drive than the table you are selecting against? And is there sufficient memory and paging space on the system to account for moving this much data along with the regular activity on the system?
mark
mark
the future will be a lot like now, only later
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 05:27 AM
тАО02-04-2004 05:27 AM
Re: Performance :SQLLoader Versus Select for Update
If this is a once off or if the table is not accessed by anyone else when you run thiss specific update, you can
- write updated rows to flat file
- truncate the table
- reload (Direct ?) into table
We had a similar pb in the past where we had to read and append a huge table with updated info. We chnage the batch so we wrote into a flat file and load append to existing table.
Regards,
Jean-Luc
- write updated rows to flat file
- truncate the table
- reload (Direct ?) into table
We had a similar pb in the past where we had to read and append a huge table with updated info. We chnage the batch so we wrote into a flat file and load append to existing table.
Regards,
Jean-Luc
fiat lux
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 06:23 PM
тАО02-04-2004 06:23 PM
Re: Performance :SQLLoader Versus Select for Update
Hi,
If I had to update millions of records I would probably opt to NOT update.
I would more likely do:
CREATE TABLE new_table as select from old_table;
index new_table
grant on new table
add constraints on new_table
etc on new_table
drop table old_table
rename new_table to old_table;
you can do that using parallel query, with nologging on most operations generating very little redo and no undo at all -- in a fraction of the time it would take to update the data.
hope this helps too!
regards
Yogeeraj
If I had to update millions of records I would probably opt to NOT update.
I would more likely do:
CREATE TABLE new_table as select
index new_table
grant on new table
add constraints on new_table
etc on new_table
drop table old_table
rename new_table to old_table;
you can do that using parallel query, with nologging on most operations generating very little redo and no undo at all -- in a fraction of the time it would take to update the data.
hope this helps too!
regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
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