Azure服务器陷入处理状态疑难解答 [英] Azure Server Stuck In Processing State Troubleshoot

查看:69
本文介绍了Azure服务器陷入处理状态疑难解答的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

尊敬的Microsoft支持,

Dear Microsoft Support,

遵循对SQL数据同步问题进行故障排除"中的建议这里:

Following the recommendation from "Troubleshoot issues with SQL Data Sync" here: 

https://docs.microsoft.com/bs-latn-ba/azure/sql-database/sql-database-troubleshoot-data-sync

我们的数据同步处于无法停止的处理状态.

We had a data sync that was stuck in the processing state which we were unable to stop. 

要强制停止它(由于尝试通过Azure门户停止它或将其删除无效),我们决定删除目标数据库.如您所料,这导致了数据同步中的错误.对于我们来说,拥有目标数据库并不是很重要的事情 或数据同步.

To force stop it (since attempting to stop it or delete it via the Azure portal didn't work) we decided to delete the destination database. This caused an error in the data sync as you'd expect. It was not high priority for us to have our destination database or the data sync.

问题在于,由于这样做,由于(源)SQL数据库中的进程运行时间较长,我们的服务器有时(并非总是)响应时间非常慢(所有客户端都被冻结).终止进程似乎可以解决速度下降问题.不确定是否已连接 数据同步问题?也许它没有正确删除.

The issue is, since doing so, our server occasionally (not always) has a very slow response time (all clients frozen) due to a long running process in the (source) SQL database. Killing the process seemed to resolve the slowdown. Not sure if this is connected to the data sync issue? Perhaps it didn't properly delete.

请注意,数据同步中的错误日志如下(没有数据库是有道理的):

Note the error log in the data sync says is following (makes sense without the database):

数据库重新配置失败,出现异常"SqlException ID:c19ed8cd" -a09e-47eb-8aa8-3d19deabb2cb,错误代码:-2146232060-SqlError编号:4060, 消息:无法打开登录请求的数据库.登录失败. SqlError号:18456,消息:登录失败.有关更多信息,请向客户支持提供跟踪ID"7698e8c1-174a-4bce-a632-2b9fcb8caf71"."

Database re-provisioning failed with the exception "SqlException ID: c19ed8cd-a09e-47eb-8aa8-3d19deabb2cb, Error Code: -2146232060 - SqlError Number:4060, Message: Cannot open database requested by the login. The login failed. SqlError Number:18456, Message: Login failed. For more information, provide tracing ID ‘7698e8c1-174a-4bce-a632-2b9fcb8caf71’ to customer support."

查看Azure中长期运行的查询,最高的是我复制并粘贴在底部的与数据同步相关的查询.

Looking at long running queries in Azure, the highest was the data sync related one which I've copy and pasted at the bottom.

数据同步还会在源数据库中留下许多未清理/删除的存储过程和表.

The data sync also left lots of stored procedures and tables in the source database which were not cleaned up/deleted.

希望您可以提供帮助:)

Hope you can help :)

数据同步名称(仅我们的一个):LiveToBeta

Data Sync name (our only one): LiveToBeta

订阅ID: 4b0e728b- a402-4198-b9b9-c1bf86bb0617

(@ scopeName nvarchar ( 36 ))与众不同 ObjectType,ObjectName 来自(-给我所有唯一的适配器
(@scopeName nvarchar(36))select distinct ObjectType, ObjectName from ( -- give me all the unique adapters

推荐答案

您好,

Hello,


Please run the following query and let’s try to find evidence about the Azure SQL Database being throttled.


SELECT *


If you see avg_log_write_percent is close or equal 100% you need to scale up the tier of the database.

What about the DTU graph on the portal? Please verify if consumption of resources is reaching the limits of the tier since you added the data sync process.


Hope this helps.


Regards,

SQLCoffee.com

Alberto Morillo
SQLCoffee.com


这篇关于Azure服务器陷入处理状态疑难解答的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆