Optimizing the MIIS Database
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The performance of a server running MIIS 2003 is significantly affected by the performance of the MIIS database. To maintain optimum performance, you might need to modify the default settings for SQL Server 2000 and the MIIS database.
Configuring the Transaction Log to Optimize Performance
The transaction log significantly affects performance. A transaction can be small or large depending on the type of data processing that is required. For example, renaming a forest can require the renaming of each object in the forest. Collectively, renaming all objects in the forest constitutes a single large transaction. A transaction can also be small, such as when a single user object is changed and that change must be synchronized among other data sources. In either case, whether the transaction is small or large, the performance of the transaction log can be significantly affected by disk performance, growth, and truncation (clearing).
To optimize your transaction log, you might need to do any of the following:
Create the transaction log on a separate disk or redundant array of independent disks (RAID) device. The transaction log file is written serially; therefore, using a separate dedicated disk allows the disk heads to stay in place for the next write operation.
When using a Full Recovery or Bulk-Logged Recovery model, be sure to clear the log periodically to prevent the log from filling up and diminishing performance. For more information about backing up and truncating the transaction log, see “Scheduling Full Database Backups by Using the Database Maintenance Plan Wizard” earlier in this topic.
Never delete the transaction log file. Deleting the transaction log file can lead to corruption of the database.
When running one or more large transactions, set the log file growth percentage to a number greater than 10%, which is the default setting. A single large transaction can generate a large amount of transaction log data. If the log file growth percentage is not set high enough to handle that growth, the number of transaction log growth requests can significantly slow or stall performance.
To change the transaction log file growth
In Enterprise Manager, right-click the MicrosoftIdentityIntegrationServer database, then click Properties, and then click the Transaction Log tab.
In File Growth, select In megabytes, and then enter a number equal to 1/50th (or up to four gigabytes, whichever is less) of space available on the drive where the transaction log resides.
Clearing Management Agent Run History
Another way to optimize the performance of a server running MIIS 2003 is to regularly clear the management agent run history. You can clear run histories from the MIIS 2003 Server up to a specified date by using MIISClearRunHistory in the Resource Tool Kit for Microsoft Identity Integration Server 2003, an unsupported set of tools that is available on the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkID=22788. Clearing run histories helps minimize the amount of space required for the MIIS database.