Kbase P133250: What are the differences between Workgroup and Enterprise RDBMS in 10.1x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/08/2008 |
|
Status: Verified
GOAL:
What are the differences between Workgroup and Enterprise RDBMS in 10.1x
GOAL:
Is an Enterprise License different than the Workgroup License?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
FIX:
Enterprise RDBMS
The OpenEdge Enterprise RDBMS is designed for large user environments and the transaction processing throughput of today's most demanding on-line transaction processing (OLTP) applications. Grounded in a flexible, multithreaded, multiserver architecture, the Enterprise RDBMS is a powerful, open and large-scale enterprise database that can run across multiple hardware platforms and networks.
The Enterprise RDBMS includes all of the functionality needed to meet the most demanding OLTP requirements. These capabilities include row-level locking, roll-back and roll-forward recovery, point-in-time recovery, distributed database management with two-phase commit, integral support for fail-over cluster availability, a complete suite of on-line utilities and support for the OpenEdge ABL as well as industry-standard SQL. The unique combination of power, flexibility and ease of operation makes the Enterprise RDBMS an ideal engine for a wide range of commercial and data processing applications.
Sophisticated self-tuning capabilities make the Enterprise RDBMS easier to install, tune and manage than other products. With low administration costs, low initial cost of licenses, minimum upgrade fees and limited software implementation costs, the Enterprise RDBMS provides a significant cost-of-ownership advantage over competing databases.
Features Unique to the Enterprise RDBMS
The ability to maximize performance and scalability is found in the following Enterprise database capabilities: (more detailed information can be found in the Progress Systems Administration Guide chapter on ?Managing Progress Performance?). The following summary shows the primary features that are unique to the Enterprise RDBMS.
Large File Support
Operating systems now have the ability to support data files larger than 2 gigabytes (as an OS configuration option). The OpenEdge Enterprise database allows you to enable (up to terabyte-size) large files for the database, which simplifies management of your operation since there are fewer files to manage. The use of large files also permits increased maximum capacity for the database.
Tunable Spin Locks
-SPIN Ability to set the number of times a process retries to acquire a latch before pausing. Uses the spin lock algorithm, which is very efficient when you have multiple processors.
Asynchronous I/O Processes
Before Image Writer
The Before Image Writer improves database performance on shared memory systems by performing before-image overhead operations in the background. The Before Image Writer continually writes the filled before-image buffers to disk, making the buffers available to other client and server processes.
After Image Writer
The After Image Writer is a background process that writes AI buffers to disk soon after they are filled. If the After Image Writer is working effectively, client and server processes rarely have to wait for a modified buffer to be written to disk.
Asynchronous Page Writer
Asynchronous Page Writers improve database performance on shared memory systems by performing overhead operations in the background. They continually write modified database blocks to disk. This ensures a supply of empty buffers is available so Progress does not have to wait for database buffers to be written to disk. It reduces the number of buffers that Progress must examine before writing a modified database buffer to disk and reduces the overhead associated with checkpointing because fewer modified buffers have to be written to disk when a check point occurs. Asynchronous Page Writers are self tuning.
Quiet Points
This feature allows the system administrator to pause the database .and perform tasks such as splitting mirrors to take a backup using an online non-Progress utility. The sys admin can accomplish this without shutting down the database.
Workgroup RDBMS
The Progress Workgroup RDBMS offers many of the same powerful capabilities as the Enterprise RDBMS. It is optimized for workgroups of 2 to 50 concurrent users and provides a cost-effective, department-level solution that includes high performance, multi-user support, and cross-platform interoperability - at an excellent value. It meets the needs of workgroup applications by running on a wide variety of hardware and operating system platforms. Because the flexible database architecture provides excellent throughput on all platforms, a database deployed on one machine can serve applications on other systems and network configurations.
Note: Workgroup does not include any of the Enterprise performance features listed previously.
Enterprise vs Workgroup ? The Difference
Progress recognizes that our customers' RDBMS requirements differ depending on the size and scope of their applications. Less data-intensive applications with a modest number of users and with no real need for 7x24 availability do not require the full power of the OpenEdge Enterprise database. In such situations, the OpenEdge Workgroup database provides the optimal RDBMS solution. While it may sacrifice some of the Enterprise-level features and performance, the OpenEdge Workgroup database provides the same quality and reliability as the Enterprise database.Basically, the Enterprise database is differentiated from Workgroup database by the addition of features designed to manage large numbers of application clients and to effectively store, manage, and maintain Enterprise-level data. This includes features such as failover clusters, large files, and additional performance features. Architecturally, the Workgroup database is the same product as the Enterprise database, thus allowing an application to easily scale up or down for new markets. The basic difference between the two is in the area of scalability, performance, and feature support.
For example, should you have a small deployment of 15 users and not require continuous availability, the OpenEdge Workgroup database provides a more cost-effective option. For larger deployments of more than 65 users, Enterprise provides the strength and superior performance of an enterprise-level solution.
Since the OpenEdge Enterprise RDBMS and the Workgroup RDBMS share a common code base, applications can easily scale from small deployments up through the needs of large enterprises. The benefit of this single implementation is consistent behavior for applications, and predictable performance for a wide variety of environments.
Should your business grow from the small office of today to the larger enterprise of tomorrow, the Progress RDBMS has the scalability to grow with you. Indeed, the upgrade from Workgroup to Enterprise requires only a simple license change. No changes are needed in your application or your database for an upgrade. Instead, ?it just works?.
OpenEdge 10 Enterprise v. Workgroup RDBMS
1. Feature Comparison
The following is a summary table showing the primary features that the two products have in common (in grey) and those unique features that separate them. Architecturally, the Workgroup database is the same product as the Enterprise database, thus allowing an application to easily scale up or down for new markets.
black 1pt solid; WIDTH: 182.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: black 1pt solid; moz-background-clip: -moz-initial; moz-background-origin: -moz-initial; moz-background-inline-policy: -moz-initial" vAlign=top width=244>
Feature
Enterprise
Workgroup
Asynchronous Page Writer processes
X
Checkpoint process
ING-LEFT: 0.15in; PADDING-BOTTOM: 0in; BORDER-LEFT: rgb(212,208,200); WIDTH: 136.95pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid; BACKGROUND-COLOR: transparent" vAlign=top width=183>
X
OpenEdge Replication
X Enterprise-Enterprise*
X Workgroup-Workgroup*
Failover Cluster Support
X
h=170>
Multi-threaded Binary Dump and Reload
X
1 thread
Background I/O
X
Buffer Pools
owtext 1pt solid; BACKGROUND-COLOR: transparent" vAlign=top width=183>
X
X
Database Quiet Point
X
Multiple Brokers Per Protocol
X
X/TR>
Online Index Fix
X
X
Online Table and Index Reorganization
X
X
Online Schema Changes
class=MsoNormal style="MARGIN: 0in 0in 0pt; TEXT-ALIGN: center" align=center>X
X
Online Administration Utilities
X
X
Roll Forward Retry
X
X.
SMP Support
X
X
SMP spinlocks
variable
Set to a value of 1
OpenEdge SQL Support
ARGIN: 0in 0in 0pt; TEXT-ALIGN: center" align=center>X
X
Type II Storage Areas
X
X
Updated Two Phase Commit
X
X.
Virtual System Tables
X
X
Audit Trails
X
X
BLOB/CLOB support
yle="MARGIN: 0in 0in 0pt; TEXT-ALIGN: center" align=center>X
X
Security (SSL)
X
X
Savepoints for ABL
X
X.
JTA support
X
X
Unicode support
X
X
Add extents online
RGIN: 0in 0in 0pt; TEXT-ALIGN: center" align=center>X
X
AI Management util
X
X
Encrypting filesystem support
X
XPAN>
* Note that with the OpenEdge Replication feature, the Enterprise database can only replicate to an Enterprise database. Similarly, Workgroup can only replicate to another Workgroup database.
2. Maximum Product Limits
In the case of the Enterprise RDBMS, these limits are the maximum values allowed. For the Workgroup product, they reflect the need for Enterprise RDBMS features when exceeding the indicated values. In addition, the Enterprise database has features which make it essential for large databases, or when high user-count performance is required.
Database Parameters
Enterprise
Workgroup
=192>
Maximum Limits
Maximum Limits
Tables
32,000
32,000
Indexes
32,000
32,000
0in 0pt">Fields per table
32,000
32,000
Rows per table
9 quintillion
9 quintillion
Rows per block
256
256
class=MsoNormal style="MARGIN: 0in 0in 0pt">Concurrent Users
Up to 30,000
65
Concurrent Transactions
Up to 30,000
65
Record length
32,000 bytes
32,000 bytes
ROUND-COLOR: transparent" vAlign=top width=192>
Buffers (32-bit)
500,000 / 4GB
500,000 / 4GB
Buffer pool (64-bit)
1 billion
1 billion
Database Size
8 exabytes
15 petabytes
ORDER-BOTTOM: windowtext 1pt solid; BACKGROUND-COLOR: transparent" vAlign=top width=192>
Storage Areas
32,000
32,000
Data Area Block Size
8K Unix (4K Win)
8K Unix (4K Win)
Extent Size:
1 TB
2 GB
DTH: 2in; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid; BACKGROUND-COLOR: transparent" vAlign=top width=192>
Typical
Database size
5-10GB
3. Pragmatic Limits The Workgroup database is typically deployed for applications that have 2-50 users, and a database size of 5-10GB. At that point, the performance increases brought by the Enterprise product's asynchronous page writers and Before Image/After Image writers make a substantial difference. As database sizes and user counts increase, these Enterprise database background I/O processes keep scalability level and response times short. The workgroup product will not scale as high, nor will it support a large database online because of these key differences.
.