Differences B/W ENTERPRISE VS STANDARD EDITION FEATURES AND BENEFITS on SQL Server

 Differences B/W ENTERPRISE VS STANDARD EDITION FEATURES AND BENEFITS on SQL Server 

Enterprise	The premium offering, SQL Server Enterprise edition delivers comprehensive high-end datacenter capabilities with blazing-fast performance, unlimited virtualization, and end-to-end business intelligence - enabling high service levels for mission-critical workloads and end user access to data insights.
Standard	SQL Server Standard edition delivers basic data management and business intelligence database for departments and small organizations to run their applications and supports common development tools for on-premise and cloud - enabling effective database management with minimal IT resources.

Feature	Enterprise	Standard
Maximum compute capacity used by a single instance - SQL Server Database Engine	Operating system maximum	Limited to lesser of 4 sockets or 24 cores
Maximum memory for buffer pool per instance of SQL Server Database Engine	Operating System Maximum	128 GB
Maximum memory-optimized data size per database in SQL Server Database Engine	Unlimited memory	32 GB2

RDBMS High Availability

Feature	Enterprise	Standard
Server core support	Yes	Yes
Database mirroring	Yes	Yes Full safety only
Always On failover cluster instances	Yes 16	Yes Support for 2 nodes
Always On availability groups	Yes-Up to 8 secondary replicas, including 2  synchronous secondary replicas	No
Basic availability groups	No	Yes Support for 2 nodes
Online page and file restore	Yes	No
Online indexing	Yes	No
Online schema change	Yes	No
Fast recovery	Yes	No
Mirrored backups	Yes	No
Hot add memory and CPU	Yes	No

Ø  






































The primary data will be copied to secondary through network transaction basis. Group of database level technology. Windows Clustering setup is required without shared storage.

Ø  Combined HA / DR: - AlwaysOn provides both high availability and disaster recovery because you have live copies of your databases residing on several secondary servers. These are not just backups, but live, up-to-date copies of your databases that are usable in read-only mode.

Ø  Automatic or Manual Failover. You can set your AlwaysOn group to fail over automatically or manually. If you use automatic failover, you must also use synchronous data flow. If you are using asynchronous data flow, failover must be manual.

Ø  Enhanced Performance. Because you can offload some of these read-only and maintenance tasks to the secondary replicas, the performance of your primary replica will be enhanced. Because a lot of these operations can consume a lot of resources, offloading them will optimize the performance of your primary replica.

Ø  Failover of Multiple Databases. Databases in an AlwaysOn group will all fail over together. This is unlike database mirroring where the databases fail over individually. And it is also unlike failover clustering where the entire instance fails over.

Ø  Local or Shared Storage. Unlike failover clustering, shared storage is not a requirement with AlwaysOn. And by not using shared storage, you remove your SAN or other shared storage device as being a possible point of failure.

Ø  Automatic Page Repair. This feature is available with AlwaysOn.

Ø  Active Use of Secondaries. The databases on your secondary replicas are not just backup copies, but usable for read-only tasks. You can query the data, and do your reporting on the secondaries.   And you can direct your end-user connections to specific secondary replicas to spread out the workload.

You can also do some of your maintenance tasks on the secondary replicas: full and log backups, and integrity checks.

Ø  Availability Group Listener. We need to set up and allow for the applications to maintain connectivity to the SQL Server Databases after a failover.

A server name to which clients can connect in order to access a database in a primary or secondary replica of an Always On availability group. Availability group listeners direct incoming connections to the primary replica or to a read-only secondary replica.

RDBMS Scalability and Performance

Feature	Enterprise	Standard
Resource Governor	Yes	No
Partitioned Table Parallelism	Yes	No
NUMA Aware and Large Page Memory and Buffer Array Allocation	Yes	No
IO Resource Governance	Yes	No
Read-Ahead	Yes	No
Advanced Scanning	Yes	No

RDBMS Security

Feature	Enterprise	Standard
Transparent database encryption	Yes	No
Extensible key management	Yes	No