The same situation that we got in mssql11 now we are getting in mssql12. We have getting timeouts day a day during last weak.
always there is the same cause, abuse on mssql server.
there is no way to control it while it is occurring rather than waiting for us, customers call saying that our websites do not work ? I think the monitoring system should be improved considerably, it is not proactive.
I checked MSSQl12. There was bad brute force attack on server. I blocked a subnet on server. We are getting 15+ request in one sec ( on some seconds it was 25+). I will move one more user database to another server while they fixed there code.
I am still keeping close eye on server.
Today i checked server on your given time, but there was no abuse. I am not saying that you were wrong. I am saying we will keep checking server on that time but there was no issue today on 1-3 AM server time.
ok, but do not understand why you don’t detect this type of attack until I sent a ticket or talk to online support.
Do not you have any monitoring tool performance mssql server? Almost always you detect these attacks after me.
If you want you can use any of the urls that I have monitored. Practically in 3-5 minutes I know when there is a problem with mssql.
Ask it in the ticket and I sent one of them
Perhaps you must restrict remote conection only to your customers ( i don’t know how) . We are having a lot of attacks from remote conections
This time i was working before you send ticket. I am setting some new monitor for MSSQL12.
We have one semi dedicated server in which we blocked remote access for all IP’s except some jodohost IP and some client IP’s. Please remember in semi dedicated servers there has only 10-12 clients.
Such things are not practically possible on shared server. Customer or there developers connects servers from 100’s of locations. We can not ask for there IP’s all the time. Most of the time customers are having dynamic IP’s which change time to time. I don’t think customer will like to request us to allow there IP every time before they connect database.
I hope i am bit clear about scenario. For now, MSSQL12 is on my priority. I am keeping close eye and my team will do too.
We have some ideas on this but it will have to be a long term thing, and have development of a control panel that allows users to easily submit their IP for access on a time restricted basis, and one form does allow for all SQL servers. I have been seeing an increase in attacks on a brute force basis, and blocking dozens per day. At some point it will just be best to block all, but allow only approved. It is just a matter of getting that infastructure in place properly, and announcing it as such with time to allow people to know it ahead of time.
We continue having issues on mssql12 every day almost. You can see the stats that I posted on my ticket ERV-14029-921.
This morning we got timeouts again. I have sent my monitor error message in the ticket.
This was during backups time, I am not seeing any abuse at that time making such.
Actually, just found some and blocked the source…even though it was already gone, found in log review.
yesterday, I lost services from msql12 from 2:45 to 3:30 AM. it is not normal because it is not puntual issue. we have same alert about issue on mssql12 every day from just over 1 week
Review my ticket #ERV-14029-921 to see issues in last weekend
Services weren’t down on the server for this amount of time, we will check the ticket in full but it isn’t something that was down serverwide.
perhaps services weren’t down but as you can read in my reports, mssql didn’t worked fine in this period
we have the same issue today ! 15 minutes with errors in mssql12. Let’s see my ticket to see alersts and PLEASE, look at a solution for that.
Here you are a resume about mssql12 issues on may (domain name can be read in my ticket)
Domain3
Outages: 42
Downtime: 6 hrs, 45 mins
Uptime: 99.08%
I think the results are bad enough to consider these issues further
The issue is again here, and now it is not backup time.
Nobody has issues with mssql12? Mssql12 sometimes is very, very slow
Sorry there was no any issue on mssql12, application pool was having some issue that is fixed now.
This it correct, it wasn’t mssql12 at all but win28 again this morning like last night. We have noted this issue last night and been watching it as well, tracing it down to specific site in a pool.
http://support.jodohost.com/showthread.php?p=79270#post79270
AGAIN THE SAME ISSUE! 1 HOUR WITHOUT MSSQL12 USING WEBSITES!!! When are you fix this issue? X(
There was no issue on mssql12, I recommend updating your ticket for checking your APP POOL on the web server. That is something totally different than mssql12.