Sorry but you are wrong. I have errors in three diferent domains using mssql12, one in win28, other in win 29 and other in win31.
It’s much chance that all the different polls aplication servers have an error at the same time.
In adition, last week I sent this error to you and you say that in was a win28 pool error and it can not be beacuase my domains are in win28, win29 and win31
I’m very happy with you and your services but when there are some sqlserver issue I think your team are not investigating what they should to try to resolve it.
I have sent to you and ticket system all monitors reports saying that you have some mssql12 issue and you continue denial.
We are suffering THE SAME ISUE ALL DAYS FROM 1 MONTH AGO , at the same time , day a day.
Every time I receive a different response about the origin of the issue: database abuse, remote conections attack, backup overload, pool aplication, etc,… but the issue continues day after day
SORRY BUT THIS IS NOT AN APPLICATION POOL ISSUE. LET’S SEE YOUR LOGS
it is very curious, I opened a ticket per each domain that have bad response time (in diferent servers but all with mssql12 database ). 1 hour after that, I received support response saying that all is fine. Yes , all is fine now but , one hour before what happened? Now all is very fast (7 times faster that 2 hours ago) and nobody has done anything, is it real?
I have no answer about this and I want to know what is happening day a day with my domains. I can not write 20 tickets about the same issue every day that curiously it is fixed after “nobody do nothing”, but it is always after I write a lot of ticket about it
That is because it is not an outage, if it is an outage we write about it. I have been monitoring and not seen more than a 30 sec spike over 40% cpu, most of the time we are running less than 15% cpu on the server, RAM is good, and connections while very heavy from some users are not blocking, we have stats on these levels. An outage means the server is down, and it has not been down, there was a very quick 10 minutes off as SQL services restarted on the 9th.
There are occasional spikes to over 60% but they last only 5-10 seconds as a large query is done.
That being said we have long term plans for the SQL servers and will be blocking external connections in full, and only allowing as people fill out a form to request outside access, the IPs they will be accessing from and the purpose for access.