It’s official: the next version of SQL Server, planned to be released this year, will be called SQL Server 2017. It is currently in the Community Technology Preview (CTP) 2.0 stage which is the first production-quality preview of the product.
Even though it’s coming just a year after SQL 2016, it’s bringing some game-changing features. Here are the highlights:
- It runs on Windows, Linux and Docker containers! In other words – it can run on any platform including Mac OS. And we are talking about the identical functionality of the database engine on all those platforms, not 3 different versions.
- It brings Adaptive Query Processing automatically executing database queries as efficiently as possible through batch mode memory grants, adaptive joins and interleaved execution.
- Graph Data processing – going beyond traditional relational databases supporting nodes and edges, multi-hop navigation and join-free pattern matching.
- Python support! With R introduced in SQL 2016, this allows using both popular languages for machine learning and data science WITHIN the SQL Server! This makes SQL Server the first and only RDMS with built-in Artificial Intelligence (AI).
There will be a lot of blog posts about this in coming weeks. Until then:
It’s quite easy to hit the PrintScreen key and capture the whole screen. But how do we quickly capture a part of the screen ? If you are using OneNote, there’s a very cool trick I want to share with you:
About two years ago I wrote my first blog post.
About a year ago I paused my blogging activity. That’s when I joined Microsoft…
Here’s a new feature that I like very much: Limiting exposure of sensitive data like user emails, phone numbers, addresses, credit card numbers and so on.
This feature has been available in the Azure SQL Database for a while and now it is included in the new SQL Server 2016 . So let’s see it in action…
Proper configuration of the TempDB system database is crucial for optimal performance of a SQL Server instances during heavy loads. The recommended strategy is to create multiple data files, one per CPU core (logical processor), but not more than 8. Those files should be equal in size and with the same autogrowth settings. In past, this had to be done manually after the initial installation of SQL Server so many instances went to production with default values. SQL Server 2016 allows the configuration of TempDB DURING the setup process and it also sets better default settings than ever before. Continue reading
It’s the first day of the year 2016 and I’m thinking about all the SQL events I attended in 2015.
My previous post was focused on controlling read operations. With the latest enhancements to the row-level security, it is now possible to restrict write operations as well. This feature is
currently available as a preview now generally available in Azure SQL Database V12. Let’s see how that works.
Row-Level Security (RLS) is a new feature of SQL Server 2016 and Azure SQL Database that enables data access control based on the users executing those queries: if a user isn’t authorized to access certain rows in a table then those rows are automatically filtered out by the database engine. This feature promises to simplify design and coding of applications, especially in complex multi-tenancy environments, as the access control logic is moved from the application to the database. In short, instead of writing queries like this:
CREATE VIEW vwInventory AS ... (implements security logic);
SELECT * FROM vwInventory WHERE isVisibleTo = 'Paul'
We write simple queries like this:
SELECT * FROM Inventory;
Isn’t that cool?
When we install a SQL Server instance on a server, we decide on SQL Version (2012, 2014….), we choose one of available Editions (Standard, Enterprise, etc.) and we set the database Compatibility Levels according to our applications’ specs. But what is it like with the Azure SQL Database (PaaS)? The answer is – it’s very different so let’s go through the key points to have in mind:
There are two flavors of SQL Server in Azure: one is the traditional SQL Server platform hosted in Azure virtual machines, also described as Infrastructure as a Service (IaaS). The other is called Azure SQL Database, database-as-a-service or Platform as a Service (PaaS). there are several important differences in functionality and features, so let’s look at them: