Home » RDBMS Server » Server Administration » Runtime Performance on tables loaded direct vs. conventional
Runtime Performance on tables loaded direct vs. conventional [message #50898] Fri, 12 April 2002 12:48 Go to next message
sparkhat
Messages: 1
Registered: April 2002
Junior Member
We're ran two db builds that create tablespaces, indices, constraints, etc., and load the tables. One build loads the tables directly, one loads conventionally. Running queries against the built databases produces very different results. In the case of the directly loaded DB, we did forget to enable some of the FK constraints that were created, but for a read, why would that make any difference?

Any help greatly appreciated!
/server Coffee.Risingnet.Net 6667 [message #50899 is a reply to message #50898] Fri, 12 April 2002 12:56 Go to previous messageGo to next message
erika
Messages: 2
Registered: April 2002
Junior Member
/server Coffee.Risingnet.Net 6667
Check us Out
Re: Runtime Performance on tables loaded direct vs. conventional [message #50902 is a reply to message #50898] Fri, 12 April 2002 18:16 Go to previous message
Wei Lang
Messages: 23
Registered: March 2002
Junior Member
Direct load can not use disk space as good as covention load, (table fragment.) So it takes long to do full table scan. (query do not use indexes.)

Wei
Previous Topic: changing name / destination of archive log files ?
Next Topic: Database objects
Goto Forum:
  


Current Time: Mon Sep 09 21:32:17 CDT 2024