There are many database technologies available on Azure that you can choose from. Why would you use Azure SQL?
There are so many new solutions, some very specialized and super cool, so you may be wondering why I'm telling you to use Azure SQL for your next project.
According to David - “after I joined the Azure SQL PM team, I discovered that there are many, in fact, many features that developers don't know exist…” as a result, Azure SQL is still used as if its development and evolution stopped 20 years ago… when Azure SQL was not yet there, and only its local brother, SQL Server, existed. Well, a lot of improvements have been made, really making Azure SQL definitely a native database for the post-relational cloud. Let me show you why, using just 10 simple points. I will go over each point in detail in the next blog posts.
Batteries Included in Azure SQL
Azure SQL is the relational and post-relational database that I would like to say that has “batteries included”. “Davide”, in his post borrowed that term from the Python, one of my favorite languages, and this is also the main reason why it is a great database for developers.
Many features that you would normally find in different, more specialized products are integrated into just one. Using different specialized products can bring great advantages, but it also represents a great challenge: data must be moved around all these products and the responsibility for maintaining consistency rests on the shoulders of the developer.
This is a major problem that will increase the complexity of the application by an order or magnitude. And, as a developer, I prefer to follow the KISS principle. Azure SQL allows me to focus only on what is unique to my company and application, delegating all data-related responsibilities to something that specializes in it. This is a great victory for everyone.
Post-relational resources for modern applications
JSON is what developers love and breathe, so native support for JSON is essential for a modern database. Azure SQL provides very good support for generating, consuming, manipulating and querying JSON. But that is not enough.
Graphical support, through node and edge types, transitive closure and the ability to arbitrarily navigate deep relationships using a very concise (similar to the well-known “Cypher”) is available in Azure SQL immediately.
This makes it easier to store geospatial data and query data for closer locations, find all locations within a given perimeter (perfect for geofencing) or, more generally, perform complex geospatial manipulations.
Full storage control and abstraction with Columnstore and Rowstore
With Azure SQL, you can decide whether to save a table using a technique line by line or column by column. Or a mixture of the two. And this is truly a killer feature, as it allows the creation of solutions that can quickly access a single line or can easily read, aggregate and analyze hundreds of millions of lines.
Ultra-high concurrency with tables optimized for lock-free memory
At memory-optimized tables use a sophisticated non-blocking mechanism known as Multiversion Concurrency Control (MVCC), to ensure extremely high competition and still provide full transactional support. Extremely high means hundreds of thousands of transactions per second and much more.
Time travel with “As-Of” Queries
Azure SQL offers the ability to automatically track and execute queries “from” by enabling temporal tables. Changes to a table will be tracked transparently and made available through the “History” table. Again, completely transparent to applications and very useful for auditing, reporting and business analysis
There are many new features that developers still don't know about with Microsoft Azure SQL. Learn why Azure SQL is a post-relational cloud database for ten reasons, including complete storage control, easy monitoring and complete insights.