Microsoft Identity Integration Server 2003 uses Microsoft
SQL Server 2000 as its database. You can
install both MIIS 2003 and SQL Server 2000 on the same server running Windows Server 2003, Enterprise Edition, or you can install SQL Server 2000 on a remote server.
When you install MIIS 2003, a database is created in
SQL Server 2000 named
MicrosoftIdentityIntegrationServer. This database stores
data that includes the following:
Metaverse data
Management agents and run profiles
Management agent run history
Connector space data
Joiner log
Rules extensions
The MicrosoftIdentityIntegrationServer database does not
store the following:
Log files
Contents of the \MAData folder
Administrative scripts (for example, custom scheduling scripts
or .vbs scripts created during run profile configuration)
Caution
Data in the MicrosoftIdentityIntegrationServer database
should never be directly modified by the user. User modification
can cause database corruption, failure of the server running
MIIS 2003, and loss of data. During installation of
MIIS 2003, permissions to access the
MicrosoftIdentityIntegrationServer database are granted to
the Microsoft Identity Integration Server 2003 service account and to the user
account that installed MIIS 2003. You should restrict all
other accounts from accessing the
MicrosoftIdentityIntegrationServer database.
Important
It is critical that you back up the
MicrosoftIdentityIntegrationServer database that resides on
SQL Server 2000 at regular and frequent
intervals. If a computer that is running SQL Server 2000 fails or if your system crashes, you can restore
the server that is running MIIS 2003 by using the data in the
MicrosoftIdentityIntegrationServer database. For more
information, see Backing up Microsoft Identity Integration Server 2003.
You can index metaverse attributes for faster searches. Be sure
to configure the indexed attributes by using the Metaverse
Designer, not SQL Server 2000. For more
information, see Edit indexed property for an attribute.
