Forum Widgets
Latest Discussions
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.
how to export all tables from database
I'm recently started working in Microsoft Synapse and exploring the templates from the gallery available in Synapse "Database templates" and want to export all tables e.g. Automotive. I’ve tried using the DESCRIBE command, but it only gives information about a single table. How can I write a SQL query to export all tables from the database template and export it to CSV? Is there a specific system view or query I should use in Synapse to achieve this? Any help would be appreciated. Thanks in advance!
AzureSQL DB looks empty when it's not
Hi, Quite often it happens that DB does not show any items (tables, views, scripts etc. - any item) in it. At the same time one user can see everything when other not. It happens randomly to different users. For now the only way to fix that we found for now is to scale up and down the DB compute power. It's like it "resets" something and suddenly all items are visible again. We're connecting to DB cluster via MSSMS as per screenshot. Anyone know how to fix that for good?Azure Data Studio - SQL DB Project build error MSB4020
Hi folks. I'm just getting started with ADS as we need to move an existing on-prem DB to Azure. I 'm trying to use ADS to set up the target DB. I installed the SQL Database Projects extension and created a project from our on-prem DB, but every time I try to build it I get Error MSB4020: stdout: C:\Program Files\dotnet\sdk\7.0.403\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(1199,3): error MSB4020: The value "" of the "Project" attribute in element <Import> is invalid. [c:\testing\WT pre-migration\WT pre-migration.sqlproj] Here's the proj file: <?xml version="1.0" encoding="utf-8"?> <Project DefaultTargets="Build"> <Sdk Name="Microsoft.Build.Sql" Version="0.2.0-preview" /> <PropertyGroup> <Name>WT pre-migration</Name> <ProjectGuid>{AE8E25C1-F1D6-4447-A008-2C24C82B51FA}</ProjectGuid> <DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider</DSP> <ModelCollation>1033, CI</ModelCollation> </PropertyGroup> <Target Name="BeforeBuild"> <Delete Files="$(BaseIntermediateOutputPath)\project.assets.json" /> </Target> </Project>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 ?
