I have, in fact, had many cases where the support from JodoHost has been very good, but unfortunatly, my unpleasant experience last night was not my first with JodoHost Support.
The initial response…
This is how I opened the ticket:
“when I log into the control panel for stadter.com, using scadmin, I go to Databases - MS SQL - MS SQL DBs.
My user “scadmin_scuser” can successfully log into “scadmin_scmain” and “scadmin_scmem”, but when I go to add scadmin_scuser to my new scadmin_sctasks db, the user is not listed in the drop-down box for selection, therefor.. I cannot add the user to the new database.”
Could I have described in any more clearly that the login in question was an existing(and working) one?
The ‘reply’ I recieved was:
“you can find all info at
http://www.psoft.net/HSdocumentation/user/mssql_support.html”
If the Support rep were familliar with the documentation he/she refered me to, they would know that it, per the documentation(section “Adding New MS SQL Database users”), IS expected that existing(proven by the logins ability to authenticate and write to databases) logins show up in the drop down box.
Had I not clearly stipulated the the user I was trying to add to a db was an existing and working one, referral to procedures on first creating the new login would have been quite appropriate. So, how did I percieve this? It “appeared” to me that the rep responding to the ticket did not consider all of the information given to him/her before responding… a rushed response lacking in ‘care’.
I decided not to get into an email exchange and just ping the live support staff.
My disappointment deepend with the conversation that ensued. I have changed the name in the following transcript to “Support Rep”. Nothing else, including typos on both of our parts, has been altered. I am not, in any declarative manor, attempting to state that the rep that was chatting with me did not have an understanding of the relation ship and functionality between the SQL server logins and HSphere because he/she may very well have a great understanding of it, but I will say that that was my ‘perception’ that he/she did not and should have immediatly escaladed the issue or aquired assistance from peers.
The chat:
You are now chatting with ‘“Support Rep”’
“Support Rep”: Welcome to JodoHost Live Chat. How may I help you?
Gary Stadter: May I please have some assistance with RS #DEW-78710-272
“Support Rep”: we have replied your ticket
Gary Stadter: Im confused because I opened the ticket describing that when I follow the documentation, the drop down box is not getting populated.
Gary Stadter: I created the scadmin_scuser sql login quite some time ago and it has been functional.
“Support Rep”: please give me your username
Gary Stadter: the problem is that it is not showing up in the drop down box, as it should(per your documentation) when I create a new user on a DB.
Gary Stadter: my main JodoHost name? ..it is gstadter
“Support Rep”: and enduser username
Gary Stadter: end user name is scadmin
“Support Rep”: ok
“Support Rep”: please explain your issue
“Support Rep”: what you wan to say
“Support Rep”: you only have created one user yet
“Support Rep”: and it is showing that
Gary Stadter: 1) scadmin_scuser is within the dbo role on scadmin_scmain and scadmin_scmem
Gary Stadter: 2) attempt to re-create sqlk login scadmin_scuser fails.
Gary Stadter: the reason for 1 and 2 is that the user already exists.
“Support Rep”: you want to created new user
Gary Stadter: if you check the sql server, you will find that scadmin_scuser already exists.
Gary Stadter: it was added to dbo role on scadmin_scmain and scadmin_scmem a long time ago
Gary Stadter: what is broken is that for some reason, it is not properly ascociated with my account and therefor not being populated in the drop down box when I go to add a user to a db.
Gary Stadter: (in HSphere)
“Support Rep”: but what actually you want to do, please explain that
“Support Rep”: i am not getting you what you actually want
Gary Stadter: I want my existing sql login to show up in my HSphere.
“Support Rep”: there is only one login in your hsphere
Gary Stadter: I can’t “create” it because it already exists and is a member of the dbo role on two of my databases.
Gary Stadter: That is what I am saying
“Support Rep”: and that is scadmin_dbadmin
Gary Stadter: HSphere is not reflecting what is on the SQL server.
“Support Rep”: you need to create moer if you want
Gary Stadter: what is “moer” ?
“Support Rep”: more
“Support Rep”: i have create one test login
“Support Rep”: please check
Gary Stadter: checking…
“Support Rep”: similarly you can create
“Support Rep”: ok
Gary Stadter: SO your official response is that I am to “abandon” my scadmin_scuser sql login ?
“Support Rep”: sir may be that username is already used
“Support Rep”: thats why it is not creating scuser login
Gary Stadter: yes, it is mine.. that is what I have been trying to tell you. Is it your official response to me that the ms sql login scadmin_scuser on mssql10 belongs to someone other than scadmin ?
“Support Rep”: yes
Gary Stadter: ok
Gary Stadter: thank you.
“Support Rep”: you cant create same login twice, usernames are always unique
Gary Stadter: I understand that. That has never been in question. The “bottom line” here is that you are stating that SCADMIN_scuser belongs to someone other than SCADMIN.
Gary Stadter: again, thank you got your time
Gary Stadter: good bye
“Support Rep”: sir scadmin is just one login username
Gary Stadter: I would like to know how scadmin_scuser got DBO role on my databases if it is not one of my logins ???
“Support Rep”: it has no link with any other login
Gary Stadter: That is what I am sayiong !!! The HSphere LINK is broken
Gary Stadter: you have a customer whose HSphere has become unlined from one of his SQL logins
Gary Stadter: If you can’t help me, I will persue the issue via alternate avenues.
Gary Stadter: thank you.
Gary Stadter: have a good evening.
“Support Rep”: wait
“Support Rep”: < http://support.jodohost.com/showthread.php?t=10648 >
“Support Rep”: please check this link
Gary Stadter: ok, I read it. I do not see any information in that thread that is relevant to the issue being described here.
Gary Stadter: which part are you suggesting is relevant?
“Support Rep”: sir
Gary Stadter: yes?
“Support Rep”: when user login is created on mssql server10
“Support Rep”: it automatically get DBO permissions
“Support Rep”: and i think you have created scuser
“Support Rep”: but may be that was not shown or you deleted that
“Support Rep”: but on server it still exists
“Support Rep”: if you want to delete scuser then let us know
“Support Rep”: we will delete that manually
Gary Stadter: So now you are saying that scadmin_scuser does belong to user scadmin ?
“Support Rep”: no
“Support Rep”: scadmin and scuser both are user logins
“Support Rep”: 2 different login names
Gary Stadter: no they are not
Gary Stadter: scadmin is an HSphere login
Gary Stadter: scadmin_dbadmin & scadmin_scuser are ms sql logins
“Support Rep”: no one belong to each other but they belong to databases
“Support Rep”: you can access database by these logins
“Support Rep”: yes
“Support Rep”: they are ms sql logins
Gary Stadter: scadmin (without _dbadmin or _scuser) can log into ms sql ???
“Support Rep”: no
“Support Rep”: you need some ms sql login
“Support Rep”: to login ms sql
Gary Stadter: How can you say that I created scadmin_scuser and also tell me that it does not belong to HSphere login scadmin ?
Gary Stadter: the only way that users, such as myself can create SQL logins is through HSphere
Gary Stadter: when we do, our HSphere login is automatically appended to the front of the user name we create.
Gary Stadter: we are not given a choice about this.
“Support Rep”: if you need some login without that hsphere append then update in ticket we will manually create that for you
Gary Stadter: I don’t. will you not answer my questoin?
Gary Stadter: *question
“Support Rep”: which question?
Gary Stadter: Gary Stadter: How can you say that I created scadmin_scuser and also tell me that it does not belong to HSphere login scadmin
Gary Stadter: ?
Gary Stadter: if the HSphere login scadmin did not create scadmin_scuser, then which HSphere login did?
“Support Rep”: i am not saying that scuser is not created by scadmin
Gary Stadter: so it was, or you are unsure?
“Support Rep”: please hold
Gary Stadter: ok
“Support Rep”: your database was created shortly after mssql10 was opened and it had a bug that did not associate it with your login(also doesn’t bill you, so it is a freebie), you need to create a new login and DB to see it in hsphere
“Support Rep”:
Gary Stadter: So you are instructing me to delete my databases?
Gary Stadter: I have an idea…
“Support Rep”: not at all, just create a new login and new db with different names and you are free to use the existing ones freely
Gary Stadter: is the scadmin_scuser login being used by any databases other than those owned by scadmin?
Gary Stadter: (it should not be, of course)
Gary Stadter: can we not just:
Gary Stadter: 1) remove scadmin_scuser from dbo role on scadmin_scmain and scadmin_scmem
Gary Stadter: 2) delete scadmin_scuser user from dbs and remove sql login
Gary Stadter: 3) I should then be able to use HSphere to re-create the scadmin_scuser login and add it to my databases
Gary Stadter: is this doable?
“Support Rep”: yes we will do that
“Support Rep”: if you want please update ticket
Gary Stadter: thank you.
“Support Rep”: we will do this for you
“Support Rep”: i already told this in chat if you want we will delete scuser for you manually from server
“Support Rep”: welcome
“Support Rep”: please update ticket immediately
“Support Rep”: so that we will do it for you
Gary Stadter: updating it now…
“Support Rep”: ok
Gary Stadter: ticket has been updated.
Thank you.
