Azure 逻辑应用程序干扰 SQL Server 操作 - 导致节点红色超时，将消息从 IoT 设备插入 SQL DB
我在 Azure SQL Server 中有一个数据库，用于存储来自 IoT 设备的消息。这些设备定期向侦听器发送消息，该侦听器已设置（以及最终进入 SQL DB 之前的大量逻辑）并在 Node-Red 中运行。现在几周一切都运转良好。
输入逻辑应用程序。我有一个简单的触发器，它按计划执行两个存储过程（一个在一个表上发出重大更新，该表也用于触发器（在 SQL 中的表上）在节点红色插入数据时触发，第二个将数据插入到馈送 PowerBI 的表中两次执行的总运行时间不到 20 秒，
连接到服务器时，node-red 开始超时：3 天没有问题，启用了逻辑应用程序触发器。我可以看到保存在的不完整数据DB。它甚至不需要运行，只是启用会导致问题。
由于同样的问题，它上周被禁用了，尽管我们当时不知道这就是原因，而且我们认为这就是原因。但我们花了一些钱并进行了升级，但我可以肯定地说，这是 3 天内在 Azure 上进行的唯一更改，
我有点困惑 - 不确定发生了什么。 ，所以不知道如何解决它除了再次禁用触发器。到底是怎么回事？
I have a database in Azure SQL Server, which stores messages from IoT devices. Those devices send periodic messages to a listener which is set up (along with a lot of logic before it ends up in SQL DB) and runs in node-red. Everything works well for a couple of weeks now.
Enter Logic Apps. I have a simple trigger that executes two stored procedures on a schedule (one issues major update on one table that is also used in trigger (on a table in SQL) firing when node-red inserts data, second inserts data into a table feeding PowerBI dashboard. Total runtime for two executions is less than 20 seconds.
The moment this trigger is enabled, node-red starts experiencing time-outs when connecting to the server. And I am literal: for 3 days no issues, enabled Logic Apps trigger and I can see incomplete data saved in DB. It doesn't even have to run, just enabled causes issues.
It was disabled last week due to same issues, though we didn't know then this was the cause. We assumed neighbors were crowding us and tier was low on that db. But we forked out some cash and upgraded. Yet problem is back. And I can definitely state this is the ONLY change that was made on Azure in regards to that setup in 3 days.
I am kinda stumped - not sure what is happening, so not sure how to fix it except disabling trigger again. What is going on?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论