Restrictions of Denodo Standard¶
Denodo Standard is built on the same engine as the Denodo Platform but some of the features of the Denodo Platform are not available or are restricted.
Components of Denodo Platform Not Available In Denodo Standard
The following components of the Denodo Platform are not available in Denodo Standard:
Features Not Available in Denodo Standard
In Denodo Standard, the following features of the Denodo Platform are not available or are restricted:
Restrictions of Denodo Standard |
|
|---|---|
CPU restrictions: maximum number of cores |
8 cores in the staging and production environments 4 cores in the development environment |
Maximum number of data sources |
5 |
Maximum number of concurrent requests |
5 for the development environment. There is no limit for the staging nor the production environments. |
Disabled. With Denodo Standard you cannot store your work in a Version Control System such as Subversion, GIT, etc. This applies to Virtual DataPort and the Solution Manager. |
|
Disabled |
|
Disabled |
|
The license is fixed |
It is not possible to install another license. |
Restrictions in the Solution Manager of Denodo Standard
The following features of the Solution Manager are not available or are restricted in the Solution Manager of Denodo Standard:
You need to use the automated cloud mode to install the components of Denodo Standard (Virtual DataPort and Scheduler). |
|
Setting a custom AMI |
You have to use the AMIs provided by Denodo to install the components of Denodo Standard. |
Number of environments |
One environment per license scenario. That is, you can create one environment for production, one for development, etc.; not more. |
Instance types |
There is a limit on which type of AWS instance you can choose to install the components of Denodo Standard. |
Number of servers per cluster |
You can create one Virtual DataPort server and one Scheduler server per cluster; not more. |
Using an external database to store the configuration of the Solution Manager |
Disabled |