My other post about the continuing SQL issues with a new website connected to mssql2 got moved into some private forum, almost like JH personnel are ashamed of how it’s been handled.
When can I get some answers Stephen?
How can I get that domain moved from it’s current “cluster” over to the same servers where my other domains are located? The other sites connected to mssql1 work FINE. Performance on mssql2 SUCKS!
It’s looking more and more like my time at Jodo may be coming to and end. If this is what support around here has come to…
what do you want? i answered your questions, you want screenshots of the server?!
I have checked it out, there was some mild abuse this morning it was fixed in a few minutes and fine thereafter.
I am not the only one here, I cannot address every issue via forums, and we have very aware and able technical staff, they along with myself work the tickets.
The other forum is for archived server issues, and it was dealt with and therefor moved, (with a redirect left)
give the ticket ID and we’ll deal with it there, this isn’t a server abuse issue if you are still having problems.
What do YOU want Stephen? Screen shots of the SQL time outs? SHEESH!
I DID give the ticket number (more than once) in the other post, and there was DEFINITELY something going on, abuse or not.
The website/domains resolve to the same IP, however the furyandfire site loaded MUCH quicker with ZERO sql time outs. The Maelstrom site is connected to a different SQL server, which is the ONLY difference between the sites (save graphical themes, which image size differences are negligible).
If you’re saying there’s nothing wrong with the SQL server, then I’d suggest your network group investigate the local network routes/connections between the web server and the SQL server. There is (or at least WAS) something going on that caused the SQL time outs.
It seems to be better this morning, so hopefully it’s been resolved. But if not you can rest assured I’ll be back here screaming about it since that what it seems to take to get anything fixed around here. I’m not stupid, and I’ve been doing this a LONG time. I can tell when something simply “isn’t right”, and while I may not be able to completely diagnose the problem (since I’m not there to put my hands on the hardware/tools to diagnose locally), I can certainly see commonalities and reference prior experience. Discounting customers reports of problems is a sure fire way of alienating them, and ultimately losing them. I’ve been patient with previous support situations, but this one has me reviewing other hosting providers. Congratulations.
Very disappointed in your snide response Stephen. You use to be better than that. Sounds like you’re tired of taking heat for a lackluster support crew if you ask me.
No, I have given you answers, I told you we blocked a large group of IPs, I have investigated the server and done this. I know the network fully, I know it was not the issue.
I am indeed stressed this last 3 weeks has been a pain but none of it due to my tech staff, NONE. I don’t see the need to go blabbing about every issue on the forums when you have an minor problem. (The alst 3 weeks has more jut been a storm of scheduling due to holidays, upgrades, leaves etc)
If you hate our staff so much really you’d be better just to save yourself the trouble and leave. They do their job and overall they do it well. I correct them when they make mistakes and it does happen.
I can’t see and validate every answer, it is not humanly possible, but I trust the team that has been here years now.
I am not, and will not be your conduit to getting ‘answers’ for everything, as it is not possible for me to do so. I know you may have trouble understanding it but I work almost as many hours as there are in a day on many aspects of the business and I can not tend to every answer personally.
You’ll just have to forgive me if I’m not as impressed with your support crew as you seem to be.
Every time I set up a new website I seem to jump through the same hoops trying to get everything working the way it should. Some of the problems are caused by your choice in control panels (SPF record management?), while others are related to some of the decisions regarding access to your SQL boxes (note, I CAN manage my own data on MSSQL1, but now someone came up with the bright idea to NOT allow the same level of access on mssql2? Dumb, plain and simple). That EMS Lite client is the absolute SUCK for SQL data management. Especially when I’ve already invested in MS SQL Management Studio, per JH’s suggestion I might add.
Sometimes the support staff does great. Other times it takes me coming here and giving a shout out to you before anything gets done, or done correctly at least.
I understand you can’t “be everywhere, do everything”, but it’s really tiresome to have to jump through these hoops every time I set up a new site. Surely there has to be a better solution.
For now the site seems to be working. It’s still not as fast to respond as the sites that are connected to MSSQL1, but it’s at least usable today. So far I haven’t had any time outs, and I’ll keep my fingers crossed.
In the mean time…I’m researching other options in case it goes South again. This relationship may have run its course, sadly.
These hoops you don’t have to jump through, SPF is not REQUIRED, it is suggested, you can put in a ticket for us to enable it and make the changes all at the same time, and there are many that don’t have any problem in the SPF record creation.
SQL access, MSSQL1 and 2 are configured the same, but we allow some exceptions on a case by case basis, and this was my choice due to abuses and complaints seen before. On future offerings we make no outside SQL access will be allowed at all, which is the case at many hosts. If SQL is that big of a deal blame that on me, and it isn’t going to get any easier in the future. This problem on SQL2 was caused by being open to the outside at all, even if they could not see SQL DBs or even login.
We have a proper escalation method using helpline /at/ jodohost.com that will bring tickets to manager’s attention(including me) if you do not feel it is being handled appropriately.
Ok from now on then, I won’t be helping on forums, ticket is THE means to get support not forums. These forums are for aid and help, but are not for ticket matters. Esp when there is not an issue with the SQL server as stated.
Submitting a ticket with the URL having any issue, and any relevant info is not a struggle, and will be seen to quickly now.
Stephen, I’m NOT going to be putting in a ticket just to ask the question “is there currently a problem with xxxxx server?”
If you’re not willing to answer those types of questions here so your users know whether or not it’s an actual SUPPORT TICKET type scenario, that’s just sad.
Seriously, JH is going WAY downhill. Your level of service is nowhere near what it was when I first signed up here. You need a refresher course in customer service.
YES, it IS! You want me to show you exactly how fubar that ticketing system is? I log in and can’t even see ANY ticket history. NOTHING.
What happened to the “new and improved” system you had me testing for a week or two a while back? The one I have to use due to the time I opened my account here SUCKS! PERIOD!
You can submit a ticket via email, desk, whatever, it is not a struggle.
We just need complete info in a ticket when it is submitted to handle it as quickly as possible. That includes urls, summary of the problem etc. If you don’t submit a ticket, we can’t provide proper support.
The other ticket desk still works and you can submit there if you wish no one is preventing you from sending there.
The key is a TICKET is the key to support. Most issues cannot be handled here on the forums because not enough info an be passed. Including whatever is the ‘issue’ now because I can’t see any problem on web or SQL server side.