Locking Down Features Using the Registry
Go Up to Specifying Application Preferences and Feature Options
Administrators can restrict certain features on individual machines through registry settings. Those settings are stored in the following location:
- In Rapid SQL,
HKEY_LOCAL_MACHINE\Software\IDERA\Rapid SQL\Admin
The following general datasource and connection settings are available:
| Name (and Type) | Description and Supported Values |
|---|---|
|
RestrictedPlatforms (REG_SZ) |
A comma-separated list (db2=0,mssqlserver=1, for example) dictating DBMS platform support on the machine. Valid names for the name=value pairs are db2, os390, mssqlserver, mysql, oracle, sybase, mssqlazure, odbc, jdbc, and sybaseiq. Any non-zero value for a name=value pair results in that platform not being unavailable on that machine. A zero value (the default) results in the platform being available on that machine. |
|
DisableAutoConnect (REG_DWORD) |
When set to any non-zero value, users cannot use the auto-connect feature when registering or logging in to a datasource. |
|
SharedDatasourceCatalogPath (REG_SZ) |
Providing a path to the network shared datasource catalog forces Rapid SQL to use that datasource catalog storage option. Registry-based and file-based catalog storage will be unavailable on this machine. |
UseConnect and AllowKeepMeSignedIn is type REG_DWORD (legal values for both are 0 for FALSE and 1 for TRUE).
Administrators not wanting to use these settings from the HKLM root key, can use the same options in HKCU root key:
- In Rapid SQL,
HKEY_CURRENT_USER\Software\IDERA\Rapid SQL\Admin
If the option is specified in both locations, HKEY_LOCAL_MACHINE takes precedence over HKEY_CURRENT_USER.