Progress
DataServer
for ODBC Guide
Establishing Permissions
When you use the DataServer to create a schema image in a schema holder, it accesses the associated ODBC data source. This section describes the data-source permissions required when you create, update, or connect to a schema image.
Permissions for Creating or Updating a Schema Holder
You must have select privileges on specific system tables or database catalog files in your ODBC data source to create or update a schema image for the data source. This is because the Progress Data Dictionary must access the system tables in the data source to create or update the schema image, but it cannot do so without select privileges. However, this is the only time that you need this level of privilege when using the DataServer.
The following sections list the data-source permissions required to create or update a schema holder.
- DB2
You must have at least select permission on the following system objects: systables, syscolumns, sysindexes, and syskeys.
On DB2/MVS, you must grant BINDADD permission and CREATE IN COLLECTION NULLID permission to the host user.
- Informix
Where permissions are not explicit, you must have at least select permission on the catalog files for tables, columns, indexes, keys, and/or procedures and user information.
- Microsoft Access
You must have Read Design permissions on the catalog files for tables, columns, indexes, and keys and/or procedures, and on all user tables that you want to pull.
- Sybase
Microsoft SQL ServerYou must have at least select permission on the following system objects: syscolumns, sysindexes, sysobjects, and sysusers. For SQL Server 6.5, you must also have at least select permission on the sysprocedures system object.
Permissions for Connecting a Schema Holder
When you connect to a schema holder, you can optionally also connect to an ODBC data source. To connect to the data source, you must provide a valid data-source login name and password combination at connection time (if required by the non-Progress data source). Use the User ID (-U) parameter to provide the user ID and the Password (-P) parameter to provide the password.
Your DataServer application must have the minimum data-source permission required to access data-source tables to validate schema information and allow multiple users to access tables. For example, for Sybase data sources, your application must have at least select permission on the syscolumns, sysobjects, and sysusers system objects. For details, see the documentation for your data source.
Application-specific Permissions
In addition to the ODBC data-source permissions required by the DataServer, the required permissions for users depend on the applications that they are using. For example, a user who is running a Progress application that queries but does not update the employee table in a data source must connect to the data source with a login name and password combination that provides at least select privileges for the employee table. For users who will manipulate data at runtime, the appropriate read, insert, update, and delete permissions must be granted as administered by the foreign (target) data source.
In summary, the login name (or user ID) and password combination required to run a particular application depends on the following:
NOTE: The system administrator for your ODBC data source must establish all login name and password combinations with the appropriate data-source commands and procedures. See the documentation for your data source for information on granting user permissions.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |