|
Pervasive PSQL v10 includes an enhancement to Terminal Services.
Pervasive PSQL v10 clients running within Terminal Services client sessions can now perform Pervasive PSQL administrative functions by default. For example, a user with such a client can change configuration settings for Pervasive PSQL, create DSNs, and use the Monitor utility. In prior releases, the ability to perform administrative functions was prohibited from the client.
If you want to restrict this capability, intervention is necessary from a system administrator:
Each Terminal Server client session with the database engine now counts as one user. In previous versions of Pervasive PSQL, only the session with the Terminal Server itself counted as one user.
The Pervasive PSQL Monitor utility can now differentiate each user connected to the database engine through Windows Terminal Server or through Citrix Presentation Server. (For example, "network address" ends with ":$3" if the user is in Terminal Services session number three. A local session would show "Local:$3.")
Also note that, collectively, all applications that access the database engine and run on the same machine as the database engine also count as one user. Your user count license must be sufficient for the number of users accessing the database engine.
For example, suppose that you have a user license for 20 users and your application runs on the same machine as the database engine. The application itself counts as one user. The database engine accepts up to 19 more concurrent Terminal Server client sessions and remote database sessions (19 + 1 = 20).
See also License Administrator .
|
Chapter contents
Prev topic: File Format and Page Size
|