Feedback
Did this article resolve your question/issue?

   

Article

What features separate Enterprise from Workgroup database licenses?

« Go Back

Information

 
TitleWhat features separate Enterprise from Workgroup database licenses?
URL NameP122980
Article Number000165724
EnvironmentProduct: Progress
Version: 8.x, 9.x
Product: OpenEdge
Version: 10.x, 11.x,12.x
OS: All supported platforms
Question/Problem Description
What features separate Enterprise from Workgroup database licenses?
Is an Enterprise License different than the Workgroup License?
What are the differences between Enterprise and Workgroup RDBMS
Compare a Workgroup database to an Enterprise database.
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
Workgroup licenses allow development and deployment of multi-user applications for a modest application load. As more demand is required of the application,  it may be necessary to accommodate higher user counts and larger databases, thus the need to move to the Enterprise product.

There is a real and substantial performance benefit to the Enterprise product as the table below shows, through the availability of performance features.  Benchmarks on 2-5GB databases show an order of magnitude or more difference. As more users, CPU and memory are added to the environment, the advantage of Enterprise performance over WorkGroup is rapidly apparent.

The following is a Summary Table showing the primary features that separate the two products:

Feature

Enterprise

Workgroup

After Image Writers

YES

NO

Asynchronous Page Writers

YES

NO

Before Image Writers

YES

NO

Failover Cluster Support

YES

NO

Fathom/OpenEdge Replication

YES

10.1B01 [1]

Large Files

YES

NO

Maximum Number of Users

32,000

49

Multi-threaded Binary Dump

YES

1 thread

Quiet Point

YES

NO

SMP spinlocks

YES

10.1B01 [2]

SMP Support

YES

YES [3]

Variable Database Blocksize

YES

NO

Transparent Data Encryption (TDE),  Encryption Cache Size (-ecsize)YES [4]NO
LRU Concurrency,  
(-lruskips, -lru2skips)
YESNO
Alternate Buffer Pool (-B2)YESNO
Network Prefetch tuning,
Message wait
YESNO
Multi-threaded Index BuildYES [10.2B06]NO
Multi-tenant Tables (MT)YES [5]NO
Nap Time Increment (-napinc),   Nap Time Steps (-napstep)YESNO
Table Partitioning (TP)YES [6]NO
AI Replication StreamingYES [7]NO
Multi-threaded ServerYES [7]YES
Sequences 64 bitYES [7]YES

 

[1] Although OpenEdge Replication for Workgroup was initially made available in OpenEdge 10.1B (FCS) with limited functionality, it was not a public release for Production environments.  The recommendation is to apply the  OpenEdge 10.1B01 Service Pack (or latest) should this functionality be required.

[2] Since OpenEdge 10.1B01, 10.1C, the WorkGroup database will accept a value of "-spin 1" to alleviate the issue with the OS semaphore mechanism that we employ, not scaling on SMP machines. This limitation is not specific to the Progress product. The performance differential and hence the business benefits between the Workgroup and Enterprise RDBMS editions for both single-CPU and multi-CPU environments remain unaffected - Under the same environment, Enterprise will always outperform Workgroup.

[3] Workgroup has full functionality, but none of the performance accelerators the Enterprise license provides. The operating system implementations of semaphores vary widely in performance, with SMP | NUMA systems. SMP support is available in the Workgroup product and client processes connecting to various computers in the SMP system coordinate operating through the RDBMS by means of shared memory. Please refer to OS vendor websites and blogs for further information about semaphore scalability.

[4] To enable Transparent Data Encryption (TDE), introduced in OpenEdge 10.2B, the database must have one of the following license scenarios:
  • OpenEdge Enterprise RDBMS and OpenEdge TDE or alternatively Advanced Enterprise Edition RDBMS available since OpenEdge 11.5 (for Production)
  • OpenEdge Development Server (for Application deployment)
[5] To enable Multi-Tenancy (MT), introduced in OpenEdge 11.0, the database must have one of the following license scenarios:
  • OpenEdge Enterprise RDBMS and OpenEdge Multi-tenant Tables or alternatively Advanced Enterprise Edition RDBMS available since OpenEdge 11.5 (for Production)
  • OpenEdge Development Server (for Application development)
[6] To enable (Horizontal) Table Partitioning, introduced in OpenEdge 11.4, the database must have one of the following license scenarios:
  • OpenEdge Enterprise RDBMS and OpenEdge Table Partitioning or alternatively Advanced Enterprise Edition RDBMS available since OpenEdge 11.5 (for Production)
  • OpenEdge Development Server (for Application deployment)
[7]  Features added in OE 12.0. For further information, refer: https://docs.progress.com/bundle/openedge-whats-new/page/Database.html
Workaround
Notes
Last Modified Date11/20/2020 6:57 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.