The Workgroup database license has a total process limit of 65 connected processes to the database which the license enforces. As such the WorkGroup database will be unable to handle over 66 processes (+1 is for _mprshut).
Once installed, the Workgroup Database will allow 65 connected processes to the database, this allows for batch report jobs for example. If 30 users are connecting and each user has multiple windows open, and/or there are many batch jobs, you may need more than 65 database connections but that will not be possible due to the hardlimit enforced by the WorkGroup Database License. In cases such as these, customers should consider purchasing the Enterprise database for 30 users.
The difference between the
absolute maximum (49) and the
usable maximum (30) listed in the Documentation
is due to
performance issues from spawning everything that is likely to be needed to maintain that many connections, like being able to accommodate batch jobs and applications that need client sessions to connect more than once.
In
general, the Workgroup Database License is recommended for applications where:
- Performance is not a concern
- Database is 1 to 2 GB in size or less (but no hard limit)
- 1 to 30 users
The above is perhaps best explained by way of the examples that follow. The first two are extreme examples that clarify what has already been stated. The last two are closer to reality.
Examples: Maximum Connections vs Licensed users for WorkGroup DatabaseWhere:User License = 30
-n = 65
User License Database
Count connections
TOTAL = 30 TOTAL = 65
--------------------------
EXAMPLE 1a :
1 client alone exhausts all available database connections.
No more clients can connect.
1 Client Workstation => -1 , 0
making 65 connections => 0 , -65
TOTAL 1 , 65
REMAINING 29 , 0
EXAMPLE 1b :
The user license count is reached
while there are still available database connections
30 Client Workstations, => -30 , 0
making 2 connections each => 0 , -60
TOTAL 30 , 60
REMAINING 0 , 5
User License Database
Count connections
TOTAL = 30 TOTAL = 65
--------------------------
EXAMPLE 2a :
25 clients exhaust all available database connections.
No more clients can connect.
1 Appserver Broker:
spawns 5 State-Reset Servers => 0 , -5
serves 5 users => -5 , 0
1 WebSpeed Broker:
spawns 5 Agents => -5 , -5
serves 1000 users => 0 , 0
1 WatchDog => 0 , -1
13 Client WorkStations, => -13 , 0
4 sessions each => 0 , -52
2 Batch Processes => -2 , -2
TOTAL 25 , 65
REMAINING 5 , 0
EXAMPLE 2b :
The user license count is breached,
while there are still available database connections
1 Appserver Broker:
spawns 5 Stateless Servers => 0 , -5
serves 15 users => -15 , 0
1 WebSpeed Broker:
spawns 5 Agents => -5 , -5
serves 1000 users => 0 , 0
1 WatchDog => 0 , -1
8 Client WorkStations, => -8 , 0
3 sessions each => 0 , -24
6 Batch Processes => -6 , -6
TOTAL 34 , 41
REMAINING ** -4 , 24
** License breached
In other words, the WorkGroup Database License process limit restricts the User License.
An Enterprise Database License will allow more concurrent database connections and thereby allow all 30 Users to connect in the above examples.
The 49 user limit for a Workgroup database is a licensing limit: 50 requires an Enterprise license, a 50-user WorkGroup license cannot be purchased and is well beyond the recommended maximum of 35 users for the Workgroup database. The 65 maximum connections hardlimit allows for additional connections for batch processes and multiple sessions by some users, which is why it isn't a 50-connection hard limit.
