- Sql server 2012 enterprise edition version number software#
- Sql server 2012 enterprise edition version number license#
And some folks truly need those difference makers. You are giving a few things up with Standard edition. But – can you get by with a nightly restore? Or, if you need more data recency – can a Transactional Replication work? It’s not as scary as it sounds – and you can replicate to a Standard Edition secondary, and you can even add indexes for reporting only on the subscriber – unlike an AG) If you 100% need this feature and all it brings – then you need Enterprise.
Sql server 2012 enterprise edition version number license#
Availability Groups with readable secondaries (though – those require you to know license TWO enterprise edition SQL Server instances.Some of the advanced engine features that give Enterprise Edition better scale (like read-ahead reads and other optimizations at the storage tier – though with a well-tuned database on solid IO – for a DB environment that fits in 128GB of RAM – this may not be as big of a deal as you fear).Online Index Rebuilds (but we don’t think you should be rebuilding your indexes as often as you probably do, and we don’t think you should be rebuilding when the fragmentation is as low as you are probably rebuilding at).Some of the things you miss (that link above will show the complete list) when going to Standard: If you need more than 128GB of RAM or more than 24 cores, it also does. If you truly need some of the “Performance” minded features that are a feature of Enterprise Edition, it makes sense to stay there. With fairly little effort, we saved a few clients about $60,000 – $80,000 per year respectively on their AWS licensing by bringing them from Availability Groups in Enterprise Edition to Failover Cluster Instances in SQL Server Standard. It may even be easier to test this out than you realize with VM and cloud-based environments! In short – if your workload can handle 128GB of RAM or less, 24 cores or less – and you don’t need the few enterprise features described below – perhaps you should really be considering SQL Server Standard.
You can click the links to see the evolution from 2017/2017/2014 and earlier. There’s more here at the edition feature matrix for SQL Server 2019. All security features (Always Encrypted, Server and DB audit, EKM, Backup encryption, Dynamic data masking, etc.).Encryption (Backup, TDE, Always Encrypted) – TDE/Always Encrypted are new in SQL Server 2019.Compression (Data since 2016SP1 and Backups a lot longer).Availability Groups (with some limitations, starting in SQL Server 2016).Two node (single instance) Failover Cluster for High Availability (more on this tomorrow – including how we do that with many clients in the clouds).24 Cores (or 4 sockets, whichever is lower) – Up from 16 cores in SQL Server 2014.128GB RAM – up from 64GB in SQL Server 2012 and below.
Here are just some of the things we get with SQL Server standard nowadays in SQL Server 2019: Let me phrase it this way – “Why not?” Sure there are some reasons to stay on Enterprise (See below), but many of the reasons we used to give without much thought aren’t good reasons anymore.
Sql server 2012 enterprise edition version number software#
And that’s without software assurance (which is a whole other topic for another post – navigating Software Assurance and licensing) On an 8 core server – that’s $40,000 reasons. Saving $10,000 for each 2 core pack is a good starter reason. Why Downgrade to SQL Server Standard Edition? Some folks should be on the fast track to “downgrade” from SQL Server Enterprise to SQL Server Standard. Some folks need to stay on SQL Server enterprise. The answers here are not one size fits all. Tomorrow I’ll share the link to the webinar and talk a bit more about achieving HA with SQL Server standard in the cloud. I’ll share the video from MSSQLTIPS here tomorrow when we have the link, and once I get the list of questions asked we didn’t get to – I’ll answer them here in a post tomorrow.įor now, a brief post where I’ll cover some things to think about, some reasons to consider downgrading to standard, some reasons to stay Enterprise. I just hosted a webinar today with SIOS Technologies and David Bermingham talking about that. I’ve lost track of the number of clients we’ve helped downgrade from SQL Server Enterprise to SQL Server Standard, take advantage of new features, and fairly dramatically reduce their costs.
Lately, we’ve been finding more and more folks who can answer that probably not. Do you need SQL Server Enterprise Edition? Maybe.