Author Archive for: Andreas Wolter
Entries by Andreas Wolter
Full day PreCon Practical Performance Analysis in Melbourne at Asia & Australia Tour 2018
As it has almost become a habit by now for me, I will be touring Asia this summer. This year not only Asia, but for the first time also Australia. (There, however, is winter, which sometimes leads to funny confusion in agreements until you get used to this.) 1st stop: Singapore – Azure SQL Database […]
Tracing with XEvents in Azure SQL Database
Being Developer, Administrator or simply Support for an Azure SQL Database based Application, there are those moments when the Azure-provided Dashboard-capabilities are not sufficient and you need to conduct a throughout trace of certain statements occurring.
Survey: patched for Meltdown & Spectre?
It has been over 4 weeks now that the very serious security bugs named Meltdown and Spectre, affecting almost any CPU made in the last decade, have been publicized and patches have been made available for various systems and software. Some patches even had to be withdrawn and recreated (AMD had not maintained its documentation). In […]
Separation of Duties (SoD) and role-based security conception in SQL Server
Introduction With the upcoming implementation of the European General Data Protection Regulation (GDPR) in May 2018, having a security concept in place is essentially required by law. Microsoft SQL Server, just like other database systems, carries the main asset to protect: the data itself. Therefore, it is time for an article from a more strategic […]
Optimal Cluster sizes for SQL Server on SSDs – are 64K still important?
Lately, with the advance of SSDs, more and more administrators are wondering: Is the old rule to use a 64K Cluster size (aka “File Allocation Unit size”) for SQL Server still applicable on today’s hard drives, especially SSDs or even Flash? And: Does it apply to all RAID-types equally? This summer I took some time […]
Optimizing workflows with In-Memory and Natively Compiled Objects – or how it does not work
During the course of optimizing data-access-code with the In-Memory-functionalities in Microsoft SQL Server (memory optimized tables + indexes, memory optimized table valued parameters and natively compiled stored procedures), you may often realize that sometimes you go one step forward and then another one backwards.
