Is there a performance overhead using Composite Primary Indexes?

Backup Archive and Restore (BAR)
All things BAR
Highlighted
Enthusiast

Is there a performance overhead using Composite Primary Indexes?

I am going to be setting up processes to copy all the data within a database to another server.  The backups are already being created with the catalog option.   If everything is being copied from a backup, does the catalog option in the copy help in any way or does it slow down the copy?  Or is the difference too small with which to be concerned?

 

If necessary, I'll run a copy both with and without the catalog option, but the copies each take about 6 hours so I'm curious if anyone has tested the impact of using the catalog option in a copy with everything being restored.

1 REPLY
Teradata Employee

Re: Is there a performance overhead using Composite Primary Indexes?

Assuming you are referring to the CATALOG run-time option for ARC, only use CATALOG for a COPY operation if you are restoring relatively few of the objects on the backup file.

In your case, it won't help. And if the media being used is a physical "streaming" tape transport, it will cause significant slowdown to explicitly position to each object within the file, versus just reading sequentially.

 

How does this question relate to the Subject line?