| Feature | Enterprise | Standard |
| User instances | No | No |
| LocalDB | No | No |
| Dedicated admin connection | Yes | Yes |
| PowerShell scripting support | Yes | Yes |
| SysPrep support 1 | Yes | Yes |
| Support for data-tier application component operations - extract, deploy, upgrade, delete | Yes | Yes |
| Policy automation (check on schedule and change) | Yes | Yes |
| Performance data collector | Yes | Yes |
| Able to enroll as a managed instance in multi-instance management | Yes | Yes |
| Standard performance reports | Yes | Yes |
| Plan guides and plan freezing for plan guides | Yes | Yes |
| Direct query of indexed views (using NOEXPAND hint) | Yes | Yes |
| Automatic indexed views maintenance | Yes | Yes |
| Distributed partitioned views | Yes | No |
| Parallel indexed operations | Yes | No |
| Automatic use of indexed view by query optimizer | Yes | No |
| Parallel consistency check | Yes | No |
| SQL Server Utility Control Point | Yes | No |
| Buffer pool extension | Yes | Yes |
Logged operations are replicated. These include, but are not limited to: DDL DML Create/alter table space Create/alter storage group Create/alter buffer pool XML data. Logged LOBs Not logged operations are not replicated. These include, but are not limited to: Database configuration parameters (this allows primary and standby databases to be configured differently). "Not logged initially" tables Not logged LOBs UDF (User Defined Function) libraries. UDF DDL is replicated. But the libraries used by UDF (such as C or Java libraries) are not replicated, because they are not stored in the database. Users must manually copy the libraries to the standby. Note: You can use database configuration parameter BLOCKNONLOGGED to block not logged operations on the primary.
Comments