Forum Widgets
Latest Discussions
Azure SQL DB Index Recommendations
For the SQL Azure Databases in multiple regions and multiple subscriptions, we keep getting recommendations/warning regarding the addition of indexes is required, but those recommendations are implemented already and those indexes exist. We understand that manually applied recommendations will remain active and shown in the list of recommendations for 24-48 hrs. before the system automatically withdraws them but it's a recurring issue for them and is causing lot of churn. Basically we want to understand if the recommendation has already been applied why is the base issue not resolved? Will they be there forever or is there a way to force the recommendation to be evaluated again. Thanks.
Query from Excel in Synapse Serverless
I'm trying to use the following code to read from an Excel file using Synapse Serverless. Is this even possible? SELECT * FROM OPENROWSET('Microsoft.ACE.OLEDB.12.0','Excel 12.0 Xml;HDR=YES;Database=https://container.blob.core.windows.net/datalake/Bronze/Manual/Testing 20230106.xlsx', 'SELECT * FROM [ProductList$]') AS ROWS; I'm getting an error near Openrowset which is less than helpful from the Synapse Serverless SQL engine
Azure SQL Database
Hi, i currently have a Microsoft Access application that uses data, queries, forms, report and custom vb coding. I'm looking for a modern cloud solution that i can use to recreate my application and then be able to offer to my clients via web link. Is Azure SQL database a reasonable tool for this high level requirement?AZURE SQL DB Deadlock
I see more than 2000 deadlock everyday for my Azure SQL DB in deadlock metrics but at the end it is not causing any missing data or any transaction drop. My application not using any retry logic then how it is possible that deadlock is getting automatically resolved has no impact at all ?
Extend the period of storing telemetry of all services of my subscription.
I have had now 4 support cases in which i see strange behavior of my services in the Azure cloud. For this i created support cases. We are a software company building solution on the Microsoft stack. In case of an incident we first look to our solution and will do an RCA. Sometimes the root cause is not related to our solution but to the Azure services. When seeing this we create a MS support case. It will take some time for MS to understand the case. A lot of time the case, is moved to different engineers. Because of this we run out of the 30 days for which telemetry of our services are available for the MS engineers. So we loose all interesting data to find the Root cause. Please extend the 30 days. This is really too short for analyzing situations. In our company we store telemetry information for 1 year. It is not acceptable for our customers that we do not know the root cause of the incident.
