Last week, Microsoft released its newest feature: Azure monitor. This new platform service provides monitoring for single Azure resources and can visualize, query, route, archive, and take action on the metrics and logs coming from those resources. Working in an enterprise environment, I am curious to explore how this feature provides an added value to cloud integration. In this post, I’d therefore would like to point out some interesting properties! Personally, I’ll mainly use Logical apps to investigate Azure Monitor, but those technics are, of course, applicable to other Azure resources as well.
The tempdb system database is a global resource that is part of the system database and available to all connected users in SQL Server. As such, the tempdb can be seen as the worksheet of SQL server. Any improvement to the system will automatically effect all your custom databases. It is therefore highly recommended to fine-tune the tempdb configuration as much as you can. In this blog post, I’d like to highlight some interesting ways or best practices on how to increase its performance!