AZURE SQL DB AND LOG ANALYTICS BETTER TOGETHER – PART #1
As a DBA you may want to query SQL Audit and SQL Diagnostics information. The easiest way to do this is sending to Log analytics that is part of Azure Monitor You can also send this data to Event Hubs and storage accounts. On this post I will focus on Log AnalyticsLesson Learned #392:Querying Extended Events and Sending Results via Email using PowerShell
In this article, we will explore how to leverage PowerShell to query extended events in SQL Server and send the results via email. Extended events provide valuable insights into Azure SQL performance and activity, and automating the process of querying and receiving the results can greatly enhance monitoring and analysis capabilities. We used to have this questions about how to receive an email when a live query took more than specific duration time.Principle 'XYZ' could not be found or this principal type is not supported - Azure SQL DB and MI
In this blog article, we will be discussing the possible scenarios to get the error "Principle 'XYZ' could not be found or this principal type is not supported" while adding an AAD user or group to your Azure SQL database or Azure SQL managed instance.
Learnings from the Trenches - Azure SQL Database Best Practice Performance recommendations
This article will guide you through a series of recommendations to improve performance on your database. In addition, it will refer to various public documents that can complement the actions described in this article.AZURE SQL DB AND LOG ANALYTICS BETTER TOGETHER – PART #3 - Query AUDIT data or Who dropped my TABLE?
On Azure SQL DB you can have AUDIT data saved to Storage Account, Log Analytics and Event Hub. Log Analytics will be the easiest way to investigate this data. In this post I will show how to query AUDIT data on Log Analytics.Lesson Learned #359: TCP Provider: Error code 0x68 (104) (SQLExecDirectW)
Today, we got a service request that our customer faced the following error message connecting to the database: (pyodbc.OperationalError) ('08S01', '[08S01] [Microsoft][ODBC Driver 18 for SQL Server]TCP Provider: Error code 0x68 (104) (SQLExecDirectW)'). This customer is using Python in a Linux environment. Following I would like to share my lessons learned about this error message.
