ACT Database Configuration and Modification Recommendations
Published: August 20, 2010
Updated: August 20, 2010
Applies To: Windows 7, Windows Vista
The following sections describe the recommended ACT database configurations and modifications.
ACT Database Configuration and Modification
You can create the ACT database, by using one of the following options:
While you are configuring Microsoft® Application Compatibility Toolkit (ACT) 5.6, you can use the Application Compatibility Toolkit Configuration Wizard (ACT Configuration Wizard) to create a new database.
You can run the CreateDB.sql file. Refer to the following table for the location, based on your operating system:
Operating System Location of the CreateDB.sql File
The Windows® 7 operating system
The Windows Vista® operating system
The Windows Server® 2008 operating system with Service Pack 1 (SP1)
%SYSTEMDRIVE%\ProgramData\Microsoft\Application Compatibility Toolkit\CreateDB.sql
The Windows XP operating system with Service Pack 2 (SP2)
The Windows Server 2003 operating system with Service Pack 1 (SP1)
The Microsoft® Windows 2000 Server operating system with Update Rollup 1 for Service Pack 4 (SP4)
%SYSTEMDRIVE%\Documents and Settings\All Users\Application Data\Microsoft\Application Compatibility Toolkit\CreateDB.sql
ACT Database Role Assignments
You must assign the following database roles to the specified accounts.
You must assign the db_datareader, db_datawriter, and db_owner database roles to the user and local service accounts that will be used to run the ACT Log Processing Service.
You must assign the db_datareader and db_datawriter database roles to the user account that will log on to the computer running the Application Compatibility Manager.
You must grant the following explicit permissions to each specific user on the ACT database. Without these permissions, the Application Compatibility Toolkit will fail to function for that user.
Additional ACT Database Recommendations
We also recommend that you make the following changes to the database, as a part of your deployment planning:
Create a larger database, including a larger log file size setting, and then set the growth increments appropriately. If you create a database with the default setting for data storage, then the data portion of the database will have an initial size of 1 megabyte (MB), and a growth increment of 1 MB. If you create a database with the default setting for the log file storage, then the log file portion of the database will have an initial size of 1 MB, and a growth increment of 10 percent. We recommend that you try to maintain a data-to-log file ratio of 5:1 or 4:1. For example, if your data portion is 5 gigabytes (GB), then your log file portion should be 1 GB.
Change the recovery model of your database. The default recovery model is Full, but we recommend that you change this model setting to Simple.
Separate the hard drives on which you store your data portion and log file portion. The default, unless altered by your SQL Administrator, is for both the data and log files to be stored on the same hard drive. Separating the data from the log files will reduce disk I/O contention.