What could be the problem.
Defective hardware, broken software, too small server, simple like that.
How can i schedule and make sure the IIS is RESTARTED through Batch File / s.
- Create batch file to restart IIS with Net Stop and net Start
- Schedule batch file using scheduling mechanism.
- Look for a job outside IT as a fix like that may get you fired - it is if anything only a workaround.
Application is developed in .NET and DB is SQL latest version.
Properly fully patched, also with the regular CU, that is regularly eleased (and means cumulative update)? And you talk of SQL Servr 2012, right? THAT is the latest release.
The application is hostes on cloud server
That translates to me: The application runs on an underpowered system with not enough RAM and simply overloads the server, which is most likely pathetic on the ONE important item for database servers - disc IOPS budget, which is particularly THE performance limitator and also THE bottleneck on cloud machines.
Mostly because I Have rarely seen cloud servers that are worth being mentioned when we talk of database servers. If anything, the move to the cloud sort of psuhes everyont to way too small systems.
Have you tried finding out what is wrong? Memory? Who / what uses it? The main way to fix issues like that is to start behaving like a pro and do an analysis of WHAT is going wrong.