#MICROSOFT SQL SERVER EDITIONS NEW YORK DRIVER#
#MICROSOFT SQL SERVER EDITIONS NEW YORK SOFTWARE#
#MICROSOFT SQL SERVER EDITIONS NEW YORK CODE#

I believe Microsoft's promise/vision of being able to deploy a database solution on LocalDB with all of these programmability features and then being able to run the same solution on all higher editions represents a “game changer” in the Developer space.

#MICROSOFT SQL SERVER EDITIONS NEW YORK SOFTWARE#

On the flip side of the same “driver” coin it will also help drive adoption of the “hero features” by both developers and in particular Independent Software Vendors (ISVs), who have for years complained about the lack of certain features in lower editions of SQL Server.

#MICROSOFT SQL SERVER EDITIONS NEW YORK CODE#

As Enterprise Edition is not deployed everywhere, developers tend to code for the “lowest common denominator” with respect to features. To have a consistent programmability surface area, or feature parity for Developers if your like, between all editions of SQL Server.

#MICROSOFT SQL SERVER EDITIONS NEW YORK DRIVER#

I see the primary driver for Microsoft being to reduce the friction that developers have when potentially having to develop multiple versions of what is fundamentally the same solution. I expect the primary reason for this approach has been to reduce the potential impact on existing database solutions. On a Standard Edition instance both technologies would be able to take advantage of 32GB of memory each. That means that on an Express Edition instance both In-Memory OLTP tables and Columnstore Indexes could each consume 250MB of memory above the Buffer Pool allocation. So how will features such as In Memory OLTP tables and Columnstore Indexes, which are memory hungry technologies, play within these memory limits? Instead of allocating a subset of these hard memory limits to these features, which would potentially lead Buffer Pool pressure and lack of out-of-memory problems, Microsoft have decided that these “hero” features will be able to use up to 25% of the hard memory limit for both In-Memory OLTP features and Columnstore Indexes. You might recall the SQL Server Standard Edition is currently limited to 128GB of memory, with Express Edition supporting 1GB of memory. I fully expect the feature set to potentially evolve as Microsoft embraces this 'brave new world' and gets feedback on these changes from the industry. In most cases these 'limitations' will not dramatically affect most customers as I expect them to take advantage of this new functionality using Standard Edition. This could potentially dramatically reduce the licensing cost for enterprise customers. For scale-out solutions the Head Node will need to be installed on an Enterprise Edition instance. Furthermore Polybase will only be able to be installed as a Compute Node on the lower editions. Polybase will not be available with LocalDB. Web Edition and Express Edition will be limited to 1 core per query. With Standard Edition queries will be limited to 2 cores per query. With Columnstore Indexes Microsoft will be limiting the degree of parallelism for queries used by the Database Engine. In-Memory OLTP will not be available with LocalDB due to technical limitations.

For example Change Data Capture will not work on LocalDB and Express editions due to a various dependencies. Because of the differences in how some of these editions work there will be some limitations. So from LocalDB all the way through to Enterprise Edition a developer will have the same, consistent programmability surface area.

That is quite an impressive list of functionality which will now be available in all editions. Specifically the following features will be available in all SQL Server editions: This is a first for Microsoft, who has to date only ever moved features from Enterprise Edition to Standard Edition between different versions of SQL Server. The delivery vehicle for these changes will be SQL Server 2016 Service Pack 1, which is available immediately! That’s right, all editions of SQL Server!

In an unprecedented announcement at CONNECT() //2016 in New York City today, Microsoft has announced that a number of Enterprise Edition only features will now be available in all editions of SQL Server.

Microsoft sql server editions new york