Skip to main content

SQL Server Edition wise Feature Comparison

Often we need to figure out what specific feature (or database technology) is supported in which edition of SQL Server. Fortunately a very good chart is available at http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx to answer any question related to this topic.

However below table represent some important extract which can be very handy:                                        




Feature
Core Editions
Specialized Editions
Enterprise (Developer edition has same features)
Standard
Workgroup
Web
Express
Number of CPUs
8 CPU
4 CPU
2 CPU
4 CPU
(Web Workloads Only)
1
CPU
Memory Utilization
2 TB Ram
64 GB Ram
4 GB Ram
OS Maximum
1
GB Ram
Database Size
524PB
524PB
524PB
524PB
10
GB
x32 Hardware Support
Yes
Yes
Yes
Yes
Yes
x64 Hardware Support
Yes
Yes
Yes
Yes
Yes
Data Compression
Yes




Resource Governor
Yes




IA64 hardware support
Yes




Table and Index Partitioning
Yes




Parallel Index Operations
Yes




Parallel Consistency Checks (DBCC)
Yes




Scalable Shared Databases
Yes




Indexed views
Yes




Enhanced Read-ahead and Scan
Yes




Database Mirroring
Yes (full)
Yes (Single Threaded, Safety Full Only)
Witness only
Witness only
Witness
only
Log Shipping
Yes
Yes
Yes
Yes

Clustering
16-node failover clustering
2-node failover clustering



Automatic Corruption Recovery from Mirror
Yes
Yes



Log Stream Compression
Yes
Yes



Online Indexing
Yes




Resource Governor
Yes




Backup Compression
Yes
Yes (2008 R2 onwards)



Hot-add Memory and CPU Support
Yes




Database Snapshots
Yes




Fast Recovery
Yes




Online Page and File Restore
Yes




SQL Server Change Tracking
Yes
Yes
Yes
Yes
Yes
Merge Replication
Yes
Yes
Subscriber only 
Subscriber only 
Subscriber only 
Transactional Replication
Yes
Yes
Subscriber only 
Subscriber only 
Subscriber only 
Snapshot Replication
Yes
Yes
Subscriber only 
Subscriber only 
Subscriber only 
Heterogeneous Subscribers
Yes
Yes



Oracle Publishing
Yes




SQL Server Change Tracking
Yes
Yes
Yes
Yes
Yes
C2 Complaint Tracing
Yes
Yes
Yes
Yes
Yes
SQL Audit
Yes




Transparent Database Encryption
Yes




Extensible Key Management
Yes




Hypervisor Support
Yes
Yes
Yes
Yes
Yes
Database Migration Tools
Yes
Yes
Yes
Yes
Yes
Policy-Based Management
Yes
Yes
Yes
Yes
Yes
Database Mail
Yes
Yes
Yes
Yes

Performance Data Collection
Yes
Yes
Yes
Yes

SQL Server Agent
Yes
Yes
Yes
Yes

Database Tuning Advisor
Yes
Yes
Yes
Yes

Plan Guides
Yes
Yes

Yes

SQL Profiler
Yes
Yes
Yes


Standard Performance Reports
Yes
Yes



Distributed Partition Views
Yes




Parallel Index Operations
Yes




Automatic Query-to-index-View Matching
Yes




Unlimited Virtualization
Yes




Data Compression
Yes




Change Data Capture (CDC)
Yes









Please visit at http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx for more details. Also please note that developer edition has same features of enterprise but it must be used only for development purpose. 



NB. This chart is focused on SQL Server 2008.
Labels:
Location: Greer, SC 29650, USA

Comments

Post a Comment

Popular posts from this blog

How to kill a negative SPID (like SPID -2) in SQL Server?

Rarely this scenario will arise when most likely you see this negative SPID (most likely SPID -2) is blocking other transaction causing issues. If you try to kill it using normal KILL command, it will fail reporting below error: Msg 6101, Level 16, State 1, Line 1 Process ID <SPID Number> is not a valid process ID. Choose a number between 1 and 2048 This is because of an orphaned distributed transaction ID.  Please follow below steps to kill it: Step 1: -- Find the UOW Number select req_transactionUOW from master..syslockinfo where req_spid = <SPID Number> --  <SPID Number>  is -2 most likely. Step 2: -- Copy the UOW number from Step one KILL ‘<UOW Number>’ This will kill the negative SPID resolving the issue.  However please note following points: 1. For SPID -2, you may find multiple UOW numbers. Please start killing them one by one. Typically killing first UOW will resolve the issues. (ie. will kill all UOW and release
Post a Comment
Read more

DMV/TSQL to find out basic hardware information of the SQL Server including when SQL Server started.

Please use below code: However, please be advised that it can not tell correct information around virtualization.  For example, it will show Hypervisor even if SQL runs on a physical OS where Hyper-V is on. So use this query only when you do not have sufficient access on underlying Windows Operating system to get these information directly. -- Basic hardware information for SQL Server (sys.dm_os_sys_info) /* This query is courtesy of https://sqlserverperformance.wordpress.com/. All credits goes to original author. */ SELECT cpu_count AS [Logical CPU Count] , scheduler_count , hyperthread_ratio AS [Hyperthread Ratio] , cpu_count / hyperthread_ratio AS [Physical CPU Count] , physical_memory_kb / 1024 AS [Physical Memory (MB)] , committed_kb / 1024 AS [Committed Memory (MB)] , committed_target_kb / 1024 AS [Committed Target Memory (MB)] , max_workers_count AS [Max Workers Count] , affinity_type_desc AS [Affinity Type] , sqlserver_start_time AS [
Post a Comment
Read more

‘Trace Skipped Records’ – What is this and how to resolve it while using SQL Server Profiles?

In some very rare case, you may experience a very weired message in profiler’s output as ‘Trace Skipped Records’ while you trace something on SQL Server. Screenshot of similer situation is as below: This is not an error but it comes by design of SQL Server (I believe so). When you are using SQL profiler and return data is too big to fit in the GUI (for me, it is an enormous xml), SQL Server simply prints this message and proceed to next step. Mostlikely this is to save server’s memory and performance. Although not suggested and guranteed, you can try to run a server side trace and dump data in a file which should capture all the data. However, it is strongly not recommended to run a trace on your production server from server side. Microsoft will probally document this limitation in future. More details may be found at https://connect.microsoft.com/SQLServer/feedback/details/304225/msft-edw-profiler-displays-trace-skipped-records-for-large-530kb-batch 
Post a Comment
Read more