Two month ago I deployed a new VM in Azure. I used the pre-configured "SQL Server 2016 SP1 Standard on Windows Server 2016" with 7 GB of RAM, and I chose the offered option to make backups automatically. Only other things I changed is add it to AD and put some databases (largest of ~2 GB size of backup file)
两个月前，我在Azure中部署了一个新的VM。我在Windows Server 2016上使用了预配置的“SQL Server 2016 SP1标准”，有7 GB的RAM，我选择了提供的选项来自动进行备份。我所做的其他更改是将它添加到AD并放入一些数据库(最大的备份文件大小约为2 GB)
Now the server is running a service called SqlIaaSExtension.Service which I understand is for doing these backups as well as automated patching. You can find the services description here: MS service description
现在服务器正在运行一个名为SqlIaaSExtension的服务。我所理解的服务是用来做这些备份和自动补丁的。您可以在这里找到服务描述:MS服务描述
The problem is, it keeps on building up memory until after some weeks the SQL Server itself fails to execute larger queries. A restart of the SqlIaaSExtension.Service fixes the problem, but this is not at all a sustainable solution.
问题是，它一直在构建内存，直到几周后SQL服务器本身无法执行更大的查询。重新启动SqlIaaSExtension。服务解决了问题，但这根本不是一个可持续的解决方案。
Does anybody know a working solution other then disabling the service and loosing the functionality altogether?
是否有人知道一个可用的解决方案，然后禁用服务并完全失去功能?
My setup (german):
我的设置(德国):
1 个解决方案
#1
3
I have meanwhile got some Information from Microsoft: There seems to be an error in the SqlIaaSExtension.Service which is known to MS and will eventually be fixed.
同时我也从微软得到了一些信息:SqlIaaSExtension中似乎存在错误。MS知道的服务，最终将被修复。
Workaround is:
解决方法是:
A: If you don´t need the functionality - remove this service, as indicated in the service description.
´如果你不需要的功能——删除此服务,作为服务描述中注明。
B: If you want to keep the functionality - restart the service periodically. Possibly automate via Task-planner.
B:如果你想保持这个功能——定期重启服务。可能通过Task-planner自动化。
Updated info from MS 19/07/2017: Error is identified and should be fixed in the next 7-10 Days. A mitigation is restarting the service if necessary.
2017年7月19日更新的信息:错误已经确定，应该在未来7-10天内修复。缓解措施是在必要时重新启动服务。
Updated info from MS 31/07/2017: Error should be fixed in Version 1.2.19.0. This can be checked from the Azure Portal under "extensions" in the VM-Menu.
2017年7月31日更新的信息:错误应该在1.2.19.0版本中修正。可以在VM-Menu的“extensions”下从Azure门户中检查这一点。
#1
3
I have meanwhile got some Information from Microsoft: There seems to be an error in the SqlIaaSExtension.Service which is known to MS and will eventually be fixed.
同时我也从微软得到了一些信息:SqlIaaSExtension中似乎存在错误。MS知道的服务，最终将被修复。
Workaround is:
解决方法是:
A: If you don´t need the functionality - remove this service, as indicated in the service description.
´如果你不需要的功能——删除此服务,作为服务描述中注明。
B: If you want to keep the functionality - restart the service periodically. Possibly automate via Task-planner.
B:如果你想保持这个功能——定期重启服务。可能通过Task-planner自动化。
Updated info from MS 19/07/2017: Error is identified and should be fixed in the next 7-10 Days. A mitigation is restarting the service if necessary.
2017年7月19日更新的信息:错误已经确定，应该在未来7-10天内修复。缓解措施是在必要时重新启动服务。
Updated info from MS 31/07/2017: Error should be fixed in Version 1.2.19.0. This can be checked from the Azure Portal under "extensions" in the VM-Menu.
2017年7月31日更新的信息:错误应该在1.2.19.0版本中修正。可以在VM-Menu的“extensions”下从Azure门户中检查这一点。