|
|
Log generation has some impact on performance,
but can be completely turned off while DBFastTableCopy is
copying the data. For maximum performance, tracing should
be turned off (trace level 0, which is the default).
|
Log generation has some impact on performance,
but can be completely turned off while DBFastTableCopy is copying
the data. For maximum performance, tracing should be turned off
(trace level 0, which is the default).
With tracing turned off, only information from
startup and shutdown is output to maximize performance during the
actual copy. The following information is provided.
At startup:
- Program version and copyright
- Source database path
- Destination database path
- Username for database access
- Table being copied
- Number of records in each buffer
- User set read thread count (if any)
- Trace level
- Number of read threads, write threads
- Number of buffers created
- Incremental number of rows copied
At shutdown:
- Total rows copied
- Resource elapsed time for reading and writing
- Total resource time
- Total bytes copied
- Elapsed time for program
- Performance in bytes/hour and GigaBytes/hour copied
The trace level
0 example file included here is typical for trace level
0 (no trace). Without trace, DBFastTableCopy displays the input
parameters. At the end of the copy, the performance statistics
are logged. In this example, we run TblCopy with
trace level 0.
» Continue
to the next trace level
|
