March 5, 2015 at 3:55 am
Hi Everyone
Our consultant who installed SQL2012 and sharepoint2013, which are on different VMs, has forgotten the SA password and I need it to add our backup AD account to the SA role.
If I was to change the SQL SA password... are there any consequences in doing so? SQL is only used for SharePoint 2013
Any help would be greatly appreciated...
Thanks
John
March 5, 2015 at 4:14 am
Obviously you must be some kind of administrator user yourself to change the password.
The only effect it will have is that, if anything uses the sa login to log into the server (nothing should, ideally) then the new password will have to be entered into wherever the connection string is stored.
As I say, in an ideal world absolutely nothing should be connecting to the server as sa, but only you will know if anything does.
Edit: just reread your post - "adding an AD user to the sa role"? I think you might be a little mixed up.
"sa" is a specific SQL login on the server, I think you mean that you want to add a Windows-authenticating user to the Sys Admin role which is totally different.
Changing the sa password would not affect this at all.
HTH.
March 5, 2015 at 4:53 am
Hi,
You are correct trying to add AD account to Sys Admin role but receiving the following message:
"cannot alter the server role 'sysadmin', because it does not exist or you do not have permission."
under Security\Logins\ there are 2 users and one group:
Group - BUILTIN\Administrator - Server Role "Public"
User - Domain\administrator - Server Role "Public"
User - SA - Server Role "Public" and "sysadmin"
Any ideas on how to add sysadmin role to AD backup account?
Thanks for helping....
March 5, 2015 at 5:01 am
OK, you're in a bit of a pickle here, as the server has been left in a state where there is only one login that has Sys Admin rights and you don't have the password.
Usually the best method in this case is to back up all the user databases and other important bits, put them somewhere safe, and then do a fresh installation of SQL, taking care to set it up properly this time (hint: get a Windows user - or preferably group, NOT the local admin account, set up as a Sys Admin straight away).
Then restore all the good stuff that you put to one side and you're good to go.
People have had success using methods like the one in this link http://blogs.msdn.com/b/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx but I cannot speak from personal experience as I've luckily not been faced with this problem myself.
Does any of that look useful?
March 5, 2015 at 5:13 am
Thanks for the info, much appreciated...
March 5, 2015 at 5:16 am
March 5, 2015 at 5:20 am
From just watching the first few seconds I THINK that this is similar to the method in the link I posted.
From the look of the YT comments it seems to work, so go for it!
If you are in a position to back everything up first, or at least take copies of relevant mdf, ndf and ldf files for the purposes of reattaching if it all goes horribly wrong, then...well, just take what precautions you can before doing anything rash is what I am saying.
Good luck, and let us know how you get on.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply