Reitse Eskens

At Build 2024, Microsoft announced that Copilot for Azure SQL is entering public preview. Since then, progress has been made, and Copilot is now integrated into SQL Server Management Studio.

Have you tried to find the most effective way to ingest and process your data? Were you just as confused as I was after reading all the marketing materials? Would you like to gain more insight into maximising your capacity? These are questions I've had. And ones I regularly try to help customers with. In this session, I'll help you learn the differences between Lakehouse, SQLDB, and Warehouse performance, processing speed and cost. I'll also demonstrate how the Realtime stack can serve as a viable alternative for ingestion and processing flat files in terms of speed, scalability and ease of use. After this session, you'll walk away with real-life insights from Fabric and knowledge of which buttons not to press. If you've attended the previous instalment of this session, you'll know I won't do my testing with AdventureWorks. It will be a lot of (messy) data to give Fabric a run for its capacity units!

SQL Server 2025 and Fabric offer the option to directly mirror your data from the database into Microsoft Fabric. This offloads the analytics from your on-premises environment to the cloud. Let me show you how this works, what caveats there are and how to setup security.

At Microsoft Build 2024, there was the announcement of Copilot for Azure Sql going to public preview. Now the question arises, what can this type of Copilot do for me as a DBA, Developer or any other role where I'm working with Azure Sql. To help you get started, this session will introduce Copilot for Sql to you. Let's try some different experiences, find this Copilot and let it work a bit for us. Let's dig into general questions, data related questions but also database management! Don't expect deep dives into the inner workings, but I will get a bit into the security as this is paramount in any data resource. Buck Woody once (often) said: "don't type in demos". Join this session to see me break that rule! And even better, send in your own questions and see what happens! After this session, you'll have a better understanding of how SQL Copilot can assist you in your daily work and even improve efficiency.

At Microsoft Build 2024, there was the announcement of Copilot for Azure Sql going to public preview. Now the question arises, what can this type of Copilot do for me as a DBA, Developer or any other role where I'm working with Azure Sql.

At Microsoft Build 2024, there was the announcement of Copilot for Azure Sql going to public preview. Now the question arises, what can this type of Copilot do for me as a DBA, Developer or any other role where I'm working with Azure Sql.

Have you been deploying your Azure databases and all connected resources through the portal? Are you fed-up with clicking, weird resource naming and mostly, with having to deal with changes manually?

Have you been deploying your Azure databases and all connected resources through the portal? Are you fed-up with clicking, weird resource naming and mostly, with having to deal with changes manually? If you are working in Azure and you have anything to do with data, security and the infrastructure, this session is for you! Azure Infrastructure as Code offers a plethora of possibilities, but the first time I checked it out, all I saw were Azure Resource Manager (ARM) templates. Hard to read, harder to write. They gave me headaches. It seems I wasn't the only one with that problem, because there are excellent tools to help you out! My favourite, and the one I'm using in this session is Terraform. Now why is this presenter talking about this? I've deployed a number of customer environments with this language. Whenever there's a security update, like a new policy for example, I can deploy this to all customers in minutes. I'll only have to code this once and can easily deliver it many times, saving them time and money. Resources we can spend in other areas like ETL, ELT etc. During the session, I'll demonstrate the basics of a data deployment, following the spirit of the Microsoft Well Architected Framework. I'll show you my way of working, the structure and and the end result. As securing resources and data is paramount in any cloud solution, it'll have plenty of attention in this session as well. There is no need to try and photograph what's happening on screen, all the scripts will be available after the session.

Have you been deploying your Azure databases and all connected resources through the portal? Are you fed-up with clicking, weird resource naming and mostly, with having to deal with changes manually? If you are working in Azure and you have anything to do with data and the infrastructure, this session is for you! Azure Infrastructure as Code offers a plethora of possibilities, but the first time I checked it out, all I saw were Azure Resource Manager (ARM) templates. Hard to read, harder to write. They gave me headaches. It seems I wasn't the only one with that problem, because there are excellent tools to help you out! My favourite, and the one I'm using in this session is Terraform. Now why is this presenter talking about this? I've deployed a number of customer environments with this language. Whenever there's a security update, like a new policy for example, I can deploy this to all customers in minutes. I'll only have to code this once and can easily deliver it many times, saving them time and money. Resources we can spend in other areas like ETL, ELT etc. During the session, I'll demonstrate the basics of a data deployment, following the spirit of the Microsoft Well Architected Framework. I'll show you my way of working, the structure and and the end result. There is no need to try and photograph what's happening on screen, all the scripts will be available after the session.

This session covers how to test Fabric for larger workloads. The default demo data is usually relatively small whereas a lot of companies process a lot more. This session aims at those use cases where a large dataset needs to be processed. The session goes from data ingestion to data...

Have you been deploying your Azure databases and all connected resources through the portal? Are you fed-up with clicking, weird resource naming and mostly, with having to deal with changes manually? If you are working in Azure and you have anything to do with data and the infrastructure, this session is for you! Azure Infrastructure as Code offers a plethora of possibilities, but the first time I checked it out, all I saw were Azure Resource Manager (ARM) templates. Hard to read, harder to write. They gave me headaches. It seems I wasn't the only one with that problem, because there are excellent tools to help you out! My favourite, and the one I'm using in this session is Terraform. Now why is this presenter talking about this? I've deployed a number of customer environments with this language. Whenever there's a security update, like a new policy for example, I can deploy this to all customers in minutes. I'll only have to code this once and can easily deliver it many times, saving them time and money. Resources we can spend in other areas like ETL, ELT etc. During the session, I'll demonstrate the basics of a data deployment, following the spirit of the Microsoft Well Architected Framework. I'll show you my way of working, the structure and and the end result. There is no need to try and photograph what's happening on screen, all the scripts will be available after the session.

Azure offers a large number of database tiers, from basic to Hyperscale and a lot in between. But which tier suits your load? The key is to choose the right database for your load, but how can you determine that? In this session, I'll walk you through the different options that are available and tell you about the experiences I've had when working with them. I've been involved in a number of projects and most tiers and SKU's have been tried and tested. Some were successful, some weren't but all depending on their loads and characteristics. To give each database a fair chance, I've been using a set of scripts to get a good comparison. A script that I will share with you, along with my way of using that. Azure SQL DB performance comes at a price, so I'll cover the costs as well to give a complete picture.