Duplicates in sys.query_store_wait_stats

For machine learning, or in general any data analysis task, we need data. That’s not enough because data has to be in the right shape and data wrangling is usually tedious/time consuming/character shaping experience. QueryStore is one of the most important tools in context of Performance Intelligence (synonym for gaining performance insights and making automated decisions) because it provides consistent and unified view on queries’ performance by forming multi-feature timeseries for every query-plan-interval:

First look at SSMS Vulnerability Assessment

Long awaited version of SSMS 17.4 was released few days ago and with it - new shiny Vulnerability Assessment. I decided to include it in my Autonomous Databases presentation and spend some time with it. Definitely useful but … Disappearing checks - high risk My first VA scan contained 52 tests results which is 12 more than in Azure Sql DB version (changed from 39 to 40 recently). Next scan that I run for different database showed just 50 tests - number mysteriously decreased by 2.

Last Geo-Backup in Azure Sql DW

DR in Azure Sql DW Key component of Disaster Recovery Plan for Azure Sql DataWarehouse is a Geo-Backup Policy that must be enabled and working. Geo-Backup Azure Sql Datawarehouse uses simple recovery model and special storage level backups (consistent across multiple nodes) are taken every 4-8h. Backup history is stored in sys.pdw_loader_backup_runs DMV. Minimum once a day backup is copied to paired region so RPO is 24h assuming that Geo-Backup actually works.