When we try to add a General Purpose Azure SQL Database to Basic Elastic pool, we got error “‘System’ is not a valid database edition in this version of SQL Server.”. This blog introduced the solutions and troubleshooting steps.
Auditing for Azure SQL Database tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs. And Diagnostic log for Azure SQL Database can help us to identify performance related issue.
When you delete Azure SQL Database, Portal might return error with “The database xxx on server xxxx is used by job account xxxx. Database cannot be deleted or renamed while associated with job account;”.
In recent deployments, users have encountered a significant issue with Data API Builder (DAB) failing to connect to Azure SQL Database when hosted in Azure Kubernetes Service (AKS) with redirect connection policy and private endpoint enabled. This blog post will delve into the phenomenon, its root causes, and the proposed solutions.
You might see “Set SQL Vulnerability assessment” failure in Activity log of Azure SQL Server. And in the details error, we will see below eror { "status": { "value": "Failed", "localizedValue": "Failed" }, "subStatus": { "value": "Conflict", "localizedValue": "Conflict (HTTP Status Code: 409)" }, "statusMessage": "{ "error": { "code": "SqlVulnerabilityAssessmentStoragefullApiIsEnabled", "message": "Vulnerability Assessment is enabled on this server or one of its underlying databases with an incompatible version. Additional troubleshooting information can be found https://aka.ms/SQLVAStoragelessDocumentation. " } } }
Failed to import a bacpac file to an Azure SQL Database with Error SQL72014 and SQL72045. Below is the details Error message: Error SQL72014: .Net SqlClient Data Provider: Msg 15419, Level 16, State 1, Line 1 Supplied parameter sid should be binary(16). Error SQL72045: Script execution error. The executed script: CREATE USER [medbank-sql-read-users] WITH SID = 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAADE, TYPE = X;
In Azure SQL we have two connections policies: Proxy: the default option when you connect from on-premises without any ExpressRoute or Site-to-Site VPN. This policy requires port 1433 to open to connect to the Azure SQL Database gateway.
Sometimes when we navigate to target database in Azure Portal, it might return “URI malformed” error with below callstack: "URIError: URI malformed at decodeURIComponent (<anonymous>) at https://ms.portal.azure.com/Content/Dynamic/-CDJTGN00vty.js:1:40037 at Array.forEach (<anonymous>) at new e (https://ms.portal.azure.com/Content/Dynamic/-CDJTGN00vty.js:1:39938) at new t (https://ms.portal.azure.com/Content/Dynamic/-CDJTGN00vty.js:1:41390) at t.batch (https://ms.portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:61:508) at https://ms.portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:140:3630 at https://ms.portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:2:4295 at Object.next (https://ms.portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:2:4400) at a (https://ms.portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:2:3034)"
When we setup ESP IDF Tools with VSCode, we might get error of “C:\Espressif\tools\idf-python\3.11.2\python.exe -m pip” is not valid. (ERROR_INVALID_PIP).
When we try to configure COM with ESP IDF extention in VSCode, it might return error “no such file or directory, stat ‘c:\Users\ag\esp\v5.1\esp-idf\components\esptool_py\esptool\esptool.py’”