As Microsoft states “online clustered columnstore index build enables you to optimize and compress your data with minimal downtime without major blocking operations on the queries that are executing while you are transforming the data.”
Based on one of my favourite blog posts ever about unicorns, rainbows and online index operations (https://www.sqlskills.com/blogs/paul/a-sql-server-dba-myth-a-day-830-unicorns-rainbows-and-online-index-operations/) I wanted to show that using a command such as
Checking out the transaction log in Azure SQL Database. If you are curious like me, you will want to know about what your transaction log is doing in the cloud. The following queries have been tested and run okay within Azure SQL Database it gives you some great insight. First up, the classic log_reuse_wait_desc. You can’t exactly do much with this output, more so, just to fulfill curiosity.
Have you ever wanted to capture the T-SQL, waits, sessions IDs (etc) at a specific time for Azure SQL Database? Sure there are a few ways to do this. Extended Events comes to mind but I wanted to do something different.
I seem to be writing solely about Azure so to shake things up a bit I am going back to my “roots”. In SQL Server your differential backup is cumulative and NOT incremental and a differential will contain the data that has changed since the last full backup.
Let’s dig in using DBCC PAGE.
I do not usually link straight to other blog posts or technical papers but I really had to with this one because it contains awesome information. The paper is called “Azure SQL Database for Gaming Industry Workloads” by : Pankaj Arora, Senior Software Engineer, Microsoft.
Find the link here – https://azure.microsoft.com/mediahandler/files/resourcefiles/azure-sql-database-for-gaming-industry-workloads/Azure%20Sql%20DB%20for%20Gaming%20industry.pdf
Look out for the last section regarding the future, Hyperscale databases, Gen 6 hardware and potential “serverless” offering?
It got me excited.
All About Tech 