We have an SQL Server 2014 with a lot of Jobs that are scheduled every 12AM. They are around 70-80 jobs that will run at 12 AM. All jobs run successfully, then we just noticed that we can no longer access the SQL server on a client workstation, nor telnet the port of the SQL. The services are still running but when we try to restart the SQL Service, it does not restart successfully. The only way to make this work again is to restart the server.
This is now happening for 3 days straight and we cannot isolate what may be causing this.
We have checked all the logs in SQL and even the event logs of the windows but there is nothing to show about any error that may cause this.
There is no any scheduled task outside SQL Job that are scheduled at midnight.
Hope you can help me as this is a big issue on us since this is a production server and we cannot avail to have the server to restart every day.
Related
I think this should be simple but I cannot really find a way to do it. I have some devs connecting to a remote SQL Server 2017 using SQL Server Management Studio. Sometimes they need to run queries that take several hours to complete.
However, their laptops go to sleep if they leave them overnight which sometimes breaks the process. I do not want them to RDP to the server. Is there a way (without server/SQL admin intervention) for their queries to run persistently on the server instead of their local laptops?
I know, they could just set up their laptops to just do not go to sleep. However, that is a security policy in the company and it is a huge pain in the butt to ask for a laptop to be excluded from it.
Any suggestion is welcome.
Thanks!
What kind of database is it? For example... If an MS SQL Server then you can use an SQL Server Agent which run scheduled jobs (with tasks). Is it Azure? Then use an Elastic Job. Figure that out first before you waste your time looking into a tool that is not right for your database.
I have installed SQL Server 2019 CU2 and after that SQL Server Agent start is consuming too much CPU resulting into skip job schedules.
Although the agent service is running but it looks like hang and didn't process / kick off any jobs.
Once I re-start the Agent service it starts working again (cpu = 0), but then after some time 1-2 hours CPU intake in high and jobs do not run.
Is anybody else facing same issue with SQL Server 2019 CU2?
Any help would be much appreciated.
Thanks,
There is already a thread for this on DBA StackExchange. The issue was introduced in CU2 and will be fixed in CU3. If you're facing this, the workaround is to revert to CU1 until you are able to upgrade to CU3.
Is it possible for script to run on its own on sql server when connection closes without sql server agent?
I'd like to start for example long insert script from ETL and have it run through the night without logging into remote server and running that there.
SQL Server Agent is doing the work at the moment but it would be nice to dynamically adjust those scripts in ETL software without having to change job steps in agent.
Hope there is just some obvious trick which hasn't crossed my mind :)
Sometimes our analytics server goes down and I have to use our failover server (I know, I know...). Unfortunately the tables in that server restore every 10 minutes. Is there a way to program SQL to check if a table is being restored and, if so, to periodically retry until it is?
On our SQL Server theres a SQL Job which is ran every hour. On one particular hour it doesn't seem like the SQL Job was ran, and that was due to the SQL Server Agent being stopped during a backup.
If SQL Server Agent has been stopped, are the jobs which are supposed to be ran during the time its stopped simply ignored, or ran later when SQL Server Agent is running again?
They are ignored.
You can set up a schedule to start automatically when SQL Server Agent starts if you want to do some custom logic here such as checking for missing runs (and you can assign multiple schedules to a job)