|
|
Upgrade cu bucluc...:)
-
 09-15-2008, 10:06 AM |
-
| 09-15-2008, 10:14 AM |
-
![B_gd_n[ ]Sahlean is not online. Last active: 18-12-2013, 4:54 PM](/Themes/default/images/user_IsOffline.gif)
B_gd_n[ ]Sahlean
-
-
-
Joined on 07-17-2007
-
Bucuresti
-
sysadmin
-
-
|
Re: Upgrade cu bucluc...:)
 Diana:
Poate ajută: http://blogs.msdn.com/psssql/archive/2008/09/10/upgrade-for-sql-server-2008-can-fail-if-you-have-renamed-the-sa-account.aspxhttp://www.sqlservercentral.com/Forums/Topic560965-391-1.aspxThe work-around:
The obvious work-around is to
temporarily rename the sa account back to "sa", and then run a repair
install. However, you can't rename sa, as you can't start the DB engine.
Next
I tried hacking the install/upgrade scripts referenced above to
manually insert the name of our sa user instead of "sa". This also
didn't work as SQL seemed to ignore the change - obviously it is
running these scripts from somewhere other than the filesystem
(resource DB maybe?).
I was almost at the point of nuking the install and starting again when I had one final idea:
I
created a domain user with the username "sa", and added this account to
our Database Administrators group (should also work if you add this
account to any group with sysadmin priviledges on your SQL server).
I
then started up the DB Service and... viola, upgrade scripts executed
without a hitch, and the service started! My faux "sa" user was good
enough for the scripts to execute just fine.
Final step was to
delete this domain user again, rename the "real" sa account back to
"sa", and then run a repair install (to be safe, and also to fix a few
things that got broken by the interrupted original setup).
Once that was all done, everything appears to be normal again.
I hope that helps someone out there - it took me over a day to get this fixed!
Cheers,
Matt
|
|
|
|
|