You must deploy your customized database (.sdb) files to other computers in your organization before your compatibility fixes, compatibility modes, and AppHelp messages are applied. You can deploy your customized database files in several ways, including by using a logon script, by using Group Policy, or by performing file copy operations.

After you deploy and store the customized databases on each of your local computers, you must register the database files. Until you register the database files, the operating system is unable to identify the available compatibility fixes when starting an application.

Command-Line Options for Deploying Customized Database Files

The command-line options use the following conventions.

Sdbinst.exe [-q] [-ufilepath] [-gGUID] [-n"name"] [-?]

The following table describes the available command-line options.

Option Description


Performs a silent installation with no visible window, status, or warning information. Fatal errors appear only in Event Viewer (Eventvwr.exe).

For example,

sdbinst.exe -q


Performs an uninstallation of the specified database.

For example,

sdbinst.exe -u C:\example.sdb


Specifies the customized database to uninstall by a globally unique identifier (GUID).

For example,

sdbinst.exe -g 6586cd8f-edc9-4ea8-ad94-afabea7f62e3


Specifies the customized database to uninstall by file name.

For example,

sdbinst.exe -n "My_Database"


Displays the Help for the Sdbinst.exe tool.

For example,

sdbinst.exe -?

See Also