For nonreplicated databases, the installutil sethighrecordlimit command is run on each user database that needs the higher record limit. The command can also run on all user databases associated with a schema repository by using the -all option. The installutil sethighrecordlimit can run on a database more than once, so you can use the -all option even if the command has been applied to some of the databases before.
For replicated databases, the installutil sethighrecordlimit command is used with the -for replication option. This option can be used only at the working master site and applies to the entire clan. Other sites learn about the command through synchronization. You must have upgraded all MultiSite synchronization servers to version 7.1.x. For information, see Import all MultiSite packets and Restart MultiSite synchronization and Rational Shipping Servers.
For working master sites that also have nonreplicated user databases, run the installutil sethighrecordlimit command on those databases individually or use the -all option. The -all option does not apply to replicated databases or affect them in any way.
Databases created with version 7.0 and later in an unreplicated database set use the high record limit.
Databases created with version 7.0 and later in a clan use the record limit specified by the clan, which depends on whether the clan has been enabled for high record limits or not.
To verify that the installutil sethighrecordlimit command has been run, run the getrecordlimits command on the database.