sql server 2012 enterprise edition version number

If you want to use these to boost ROLAP performance you may want EE. If you want to drop and recreate indexes for ETL loads this may reduce your run-times, particularly on incremental loads onto large incumbent data sets.ĮE has a query re-write facility (called 'automatic use of indexed view by query optimiser'). Parallel DBCC and index builds are only supported in EE. edition is only licensed on a 'Server + CAL' basis.

If you want to scale above a two socket machine then you will probably need EE.ī.I. edition only supports servers of a certain size - 64GB RAM, 4 sockets or 16 cores for the database server. Table compression may be useful for archiving old data.ī.I. This feature isn't really well documented in SQL Server circles, though, so it's hard to tell how well it works in practice.Ĭolumnstore index - if you want to use this for fast ROLAP applications (using report builder or a 3rd party ROLAP tool such as Business Objects) then you may get significant mileage from this feature on EE. If you have an application with lots of highly selective (<1% coverage) queries on a very large fact table you might get a win from star transformations. Star join transformations are only supported in EE. If you want to use table partitions to manage large data volumes you will need EE. Table partitioning is an EE only feature. If you have compliance requirements for physically secure data then the encryption and audit facilities of EE may be desirable. Some things you will need Enterprise Edition for Memory and CPU core limits do not apply to SSAS and SSRS servers. However, the additional hardware and licensing may be no cheaper than biting the bullet and getting EE. edition supports distributed partitioned views, which gives you a basic read-only sharding capability.

You can probably get away with (say) 100GB or so on BIE by applying brute force at the hardware level (fast disks).ī.I. edition, which makes it a bit more of a contender for data marts. By the look of the link, all SSAS features present in EE are present in B.I. edition seems to give you the clever aggregates (last non empty etc.) and other features that SE doesn't on the OLAP server. edition also has a limit on the number of CPU cores and memory that can be used by the database server, although this does not appear to apply to Analysis Services or Reporting Services.Ī more detailed breakdown of the S.E., B.I. If you have less than (say) 100GB of data then you can probably get by with BI edition. The EE features are mostly relevant to users with large data volumes. EE has partitioning and the rest of the large database features.

Business Intelligence edition has some useful features, like Master Data Services and non-additive aggregations (i.e.

Sql server 2012 enterprise edition version number