Im a client for years of jodohost and I have several online systems hosted with them.
I have a system that uses a MS SQL SERVER database.
It works alright for a year and now its having timeout problems.
All the pages that uses the database shows timeouts. I went to chat and it were solved two days ago, but now it happened again. Nobody gave a comprehensible explanation.
While that my client is loosing money, cause his company depends totally in this online system, they just dont give a solution.
You know I saw your chat, and we are NOT IGNORING your problem but we must know what is happening.
You refused to answer and just stated:
Im going to forums to tell about this problem!
We are trying to get info from you on what it is doing when it tries to login, but we need info FROM you to work with you to find it, there is no issue on MSSQL7 as a server, this is something we are trying to HELP you in finding why it is, but in return you must help us.
Since you have not helped I have run SQL Trace on your account and Arijeet is sending you the results in ticket. Maybe it can help you.
Last time to fix it we did a disconnect of all your users, and iisreset to remove any stale, then it worked, it is not working this time to help.
Arijeet had woke me up from my sleep to aid him in this even before you had gotten defensive with us in chat, we are just trying to help you out, not ignoring at all, ignoring would be not waking me, not attempting to help you at all.
Also, I see you are in now in SQL Management Studio,
Thats a big fat lie, I have been in chat for hours, nobody asked me nothing in the chat, I just heard excuses, and there were no valid try to solve the problem.
There is a store procedure that generates billings everyday, but it uses one connection and one database login, so what you saying makes no sense , the only explanation is that your database server is oversold. I have been adding database to mssql7 for several years, there is not limit, jodohost is loaded and just wants the get the money from the clients
You are making no sense, since mssql7 is not on for signup for years now, I don’t really want to get into a shouting match with you on this, MSSQL7 is SMALLER today than it was a year ago, simply because some have deleted their DBs and moved accounts to SQL2005 servers, and the server isn’t on for signups. We have MSSQL8/9/10/11/12 all taking sign ups since MSSQL7 was enabled, the only thing changed on MSSQL7 in the last years is less DBs than before.
I am trying to work with you to fix the problem, if you don’t desire to work with us to find why it is not working, then I will just stop checking anything with regard to it, I am not a developer and not going to tackle it alone.
There are many DB related issued that can build over time, one I know of specifically is the ‘soop portal’ it needs a few tables truncated every month or so or it gets pathetically slow, remove the data from those tables and it blazes along.
You can make DBs, but only because you are already there, no new client has made one in years. Since this the case there are less DBs there now than before.
You are fully misunderstanding everything, including the request Arijeet gave you about wanting to know what the logins were doing.
you have yet to try to work with us to solve your issue, sure go spout whatever you want on forums, it isn’t true, you are making false claims now anyway.
I’d rather work with you to fix the issue, but you don’t seem to keen to that. Maybe I should just go back to sleep?
those logs he gave me one of them is the stored procedure I told you about, that generate billings for my clients systems (gerafaturas). The other are just simple select commands that returns lists of clients, nothing special.
maybe the problem is the stored procedure gerafaturas, but there is nothing wrong with it, just that the system has thousands of users now, and I believe your server just cant handle it…
Now why don’t yo reply to us in ticket and we will discuss this rationally instead of going off on tangents.
Something is making those commands run, when you refresh a page. I am logging all commands to the DB and login for tracing, so we can find the fault, it is not on the sql server, so we need to find where it is, without your cooperation there is no need for us to spend so much time on it.
