Performance with ATTACH/DETACH with rowid

Technote (troubleshooting)


Problem(Abstract)

Performance with ATTACH/DETACH with rowid

Cause

An index is created for rowids but, is not fragmented.

Resolving the problem

An ATTACH/DETACH will cause an index rebuild

Without rowids, performance of ATTACH/DETACH is faster.

Normally DETACH command will force table to keep only data. Indexes and constraints are not inherited. But, with rowids an "index" is created that is not a fragmented index, so it will need to be rebuilt.
This action will impact the overall performance of a DETACH.

The reverse will happen with an ATTACH command.


Rate this page:

(0 users)Average rating

Document information


More support for:

Informix Servers

Software version:

9.4, 10.0, 11.1, 11.5, 11.7, 11.70, 12.1

Operating system(s):

AIX, HP-UX, Linux, Mac OS X, Solaris, Windows

Software edition:

Developer, Enterprise, Express, Growth, Ultimate

Reference #:

1431896

Modified date:

2013-08-10

Translate my page

Machine Translation

Content navigation