SA disabled and no other logins with Sysadmin...HELP!

Question

SA disabled and no other logins with Sysadmin...HELP!

ImYourDBA

SSCertifiable

Points: 5654
More actions
September 1, 2011 at 7:46 am

#256464

Okay, so we had a third party company in to do a SharePoint migration and they wanted to do the install of SQL, etc. on the servers. Well, now that I go to administer the server, I find that the only login in SQL are 'SA' which is disabled and 'BUILTIN\Administrators' which does not have SysAdmin, rather only Public and db_owner on the one user DB.
How can I get into SQL to add a Sysadmin account now? I'm baffled.
Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 1

SQLJocky (9/1/2011)
Okay, so we had a third party company in to do a SharePoint migration and they wanted to do the install of SQL, etc. on the servers. Well, now that I go to administer the server, I find that the only login in SQL are 'SA' which is disabled and 'BUILTIN\Administrators' which does not have SysAdmin, rather only Public and db_owner on the one user DB.
How can I get into SQL to add a Sysadmin account now? I'm baffled.

Don't you have any other sysadmin account than "SA"?

My blog

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 2

SQLJocky (9/1/2011)
Okay, so we had a third party company in to do a SharePoint migration and they wanted to do the install of SQL, etc. on the servers. Well, now that I go to administer the server, I find that the only login in SQL are 'SA' which is disabled and 'BUILTIN\Administrators' which does not have SysAdmin, rather only Public and db_owner on the one user DB.
How can I get into SQL to add a Sysadmin account now? I'm baffled.

The third party company must have an sysadmin account, contact them and ask them to enable the SA account for you temporaly, until you decide which account are you going to use a sysadmin.

My blog

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 3

I found this link. It may help, but I have not tried myself.

My blog

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 4

Let me know if you were able to solve your problem.

My blog

ImYourDBA SSCertifiable Points: 5654 More actions · Answer 5

So what we ended up doing was to stop the services and start in single user mode and add the new accounts.

Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 6

SQLJocky (9/3/2011)
So what we ended up doing was to stop the services and start in single user mode and add the new accounts.

I think that the problem was solved after the reboot. It is still a good idea to check the errorlogs to findout what was the cause of the problem.

My blog

Perry Whittle SSC Guru Points: 234013 More actions · Answer 7

SQLJocky (9/3/2011)
So what we ended up doing was to stop the services and start in single user mode and add the new accounts.

thats exactly the process you needed to follow

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 8

Perry Whittle (9/5/2011)
SQLJocky (9/3/2011)
So what we ended up doing was to stop the services and start in single user mode and add the new accounts.
thats exactly the process you needed to follow

I'm glad he could solved. I never had something like that. It must be very freaky 😛

My blog

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 9

SQLJocky (9/3/2011)
So what we ended up doing was to stop the services and start in single user mode and add the new accounts.

I'm glad you could solve the problem. 🙂

My blog