Sheduled SQL重启不起作用 [英] Sheduled SQL restart does not work

问题描述

您好，

  Windows 10 Pro。由于SQL服务器的周期性减速，我决定创建一个每日事件来重新启动SQL Server实例服务作为一种解决方法。所以我为该实例创建了每晚停止开始的事件：

 Windows 10 Pro. Because of periodic slowdowns of SQL server, I decided to create a daily event for restarting SQL server instance service as a workaround. So I created nightly stop-start shedule events for the instance:

  NET Stop" mssql $ myinstance" - 晚上11:30开始

 NET Stop "mssql$myinstance" - sheduled on 11:30PM

  NET Start" mssql $ myinstance" - 在晚上11点32分展示

 NET Start "mssql$myinstance" - sheduled on 11:32PM

在设置活动期间提供最高权限和密码。

Both running with highest priviledges, password provided during setting up the event.

我在2019年4月底创建了它们，它工作了几天（在"应用程序"节点下有MSSQL启动/停止事件记录），可能直到一些系统更新。从那时起，我一直无法使这些事件发生，
删除它们并再次创建，尝试了很多解决方案，没有运气。 sql server不再自动重启。在11月14日下午11点32分，唯一记录的事件是1534，我显然不应该关心，因为它只是一个通知，无法记录动作
。

I created them at the end of April 2019 and it worked for maybe few days (under "Application" node there were MSSQL start/stop  events logged), probably until some system update. Since then, I've been unable to make the sheduled events work, deleted them and created again, tried many solutions, no luck. The sql server is not restarting automaticaly anymore. The only logged event on 11:30PM/11:32PM is 1534 which I apparently should not care about, since it is just a notification that the action could not be logged.

出现这种行为的原因是什么？如何跟踪问题以找出系统尝试执行NET命令时究竟发生了什么？

Any reason for such behaviour? How can I trace the problem to find out what exactly happens when system is trying to execute NET command?

谢谢

祝你好运

Krzysiek

推荐答案

所以你有一个无法启动的计划Windows任务？我去windows论坛问那里。首先是启用日志记录并检查该计划任务的日志，但是如何/在何处执行该操作是一个操作系统问题，可能取决于您拥有的
操作系统。

So you have a scheduled Windows task that doesn't start? I'd go to the windows forums and ask there. First thing would be to enable logging and check the logs for that scheduled task, but how/where to do that is an OS question and possibly depends on what OS you have.

这篇关于Sheduled SQL重启不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！