By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,504 Members | 1,884 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,504 IT Pros & Developers. It's quick & easy.

Perf. degradation due to TIMESTAMP WITH TZ

P: n/a
We have an application that loads millions of records into a table.
Around 10 fields in this record are date fields. We perform the insert
using SQL*Loader in direct path mode. The loading takes a few hours.
Recently we had to convert the date columns to TIMESTAMP WITH
TIMEZONE(3). After doing the appropriate changes in the SQL*Loader
control file, when we performed a load, we experienced a performance
degradation of 50%.

Is the slowdown inherently due to the type of the column?
Can somebody provide any suggestions for reducing the slowdown?

Jul 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.